Before you start
Use an account allowed to manage the team. Write down the tasks the person should perform and confirm available seats before inviting anyone.
Permissions and record scope
Give people the access their work needs.
-
Team member
- Assign deliberately Assigned role
-
Assigned role
- Check permission Permitted action
-
Permitted action
- Limit records Record scope
-
Record scope
- Protect fields Sensitive-field checks
-
Sensitive-field checks
- Within granted access Authorised work
- Outside visible result Restricted records
- Authorised work
- Restricted records
Follow these steps
- Open Team & Access or the workspace user directory.
- Review the member’s identity, base role and active status.
- Use the permitted Access control to inspect the detailed settings.
- Change only the permissions needed for the agreed tasks.
- Verify the intended view with the user, without sharing your owner credentials.
Check the result
The member has the access allowed by the saved configuration, subscription and industry. A role label alone does not mean every screen is available.
If you get stuck
If an action stays locked, check both module availability and permission. The primary owner is protected from some actions in the directory.
One thing to remember
Disabling a user changes access; it is not the same as removing an employee record or deleting their historical activity. Never use a shared owner account as an access workaround.
Keep going
Still need a hand?
Tell us what you tried, what you expected and what happened. Keep passwords, API keys and private customer information out of your message.
Open a support ticket. Visitors without a workspace can contact us.
Still stuck?
Before contacting support:
- Confirm the workspace, record number, date range and status.
- Check your role permissions and the source document.
- Refresh once and search for the record before repeating a submission.
- Check the relevant guide for the next action; do not force a match, posting or approval.
If you still need help, include the page address, exact message, time, expected result and checks already completed. Never send passwords, API keys, payment-card details or provider secrets.