Understand roles and permissions

Access depends on the product, selected workspace, licensed modules, your membership and the permissions on a specific record. A guide being available does not mean that its feature is included in every plan or workspace.

Which level controls access?

Level	Meaning	Example
Product	Determines the available feature areas	Leads and real estate belong to insideCRM.
Workspace and license	Determine membership and enabled modules	Tickets must be enabled for the workspace.
Membership role	Distinguishes regular members from administrators	Administrators receive additional management permissions.
Individual permission	Allows reading, writing or a specific management action	`tickets.read` allows reading, `tickets.write` editing.
Record access	Restricts access within a module	A private folder or an unshared mailbox remains protected.

Members generally receive the business permissions of enabled modules; individual permission overrides can change these. Administrator status does not provide missing product features or licenses. The user form provides an administrator checkbox, rather than a configurable role matrix.

Common permissions

Permission	Use
`contacts.read` / `contacts.write`	Read / edit contacts
`mail.read` / `mail.write`	Read mail / send mail and edit accounts
`tasks.read` / `tasks.write`	Read / edit tasks
`tickets.read` / `tickets.write`	Read / edit tickets
`tickets.settings.manage`	Manage ticket statuses, types and other ticket settings
`files.read` / `files.write` / `files.share`	Read / edit / share files
`vault.read` / `vault.write` / `vault.share`	Read / change / share password-safe entries
`management.read`	Open management overview and API-key list
`users.manage`	Manage users
`settings.manage`	Change central settings and API keys

Individual guides explain additional requirements. Mailbox managers, project members and safe administrators have different responsibilities; one role does not replace the others.

insideBase workspaces

Distinguish your personal workspace from a team workspace. A personal workspace has no team management or file/safe sharing permissions. Switch to the appropriate team for shared work. Use the other product's application to change products.

Change administrator status

Open Management → Users in the relevant workspace.
Find the person and open Edit. Verify their business identity.
Change the administrator checkbox only when the person should gain or give up management responsibilities. Complete reauthentication if requested.
Save and verify the required workflow using the affected account.
Transfer shared data, mailboxes and safes before withdrawing access. Do not work around an error protecting the last administrator.

If access is missing

Observation	Next step
An entire area is missing	Ask an administrator to check the product, workspace and licensed modules.
Reading works but editing is unavailable	Check write permission and the record's state.
Only certain records are missing	Check filters, ownership and sharing.
Management does not open	Check administrator status and the required management permission.
Another administrator sees more	Compare memberships and individual overrides; do not share accounts.