> For the complete documentation index, see [llms.txt](https://help.workdigital.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.workdigital.io/custom-database-apps/user-permissions/levels-of-access-controls.md).

# Levels of Access Controls

WorkSmart provides different ways on controlling and managing access to your data within your WorkSmart portal.

Following are the different ways of access management availbable in WorkSmart:

1. Contact Groups - the setup access permissions at all app level using Contact Group. Any user added to a Contact Group automatically gets access to all the apps where this Contact Group is setup as part of the User Permissions
2. All Site Members - this is a special group created for each site - Any user added to a site gets access to all the apps where "All Site Members" is setup as part of the User Permissions
3. Individual access - you can add access for a specific user to a specific app
4. Via User Based Field - if you have a User field in an app, you can enable access control based on that field. This is a very powerful feature where you can control access for each record based on the value of the User field of that record - so need to worry about setting up access in any other way.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.workdigital.io/custom-database-apps/user-permissions/levels-of-access-controls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.