Help Center / Troubleshooting /
Permission and access issues
Permissions are role-based, with per-entity overrides that can further restrict or grant access. When a feature or entity isn't visible, the answer is almost always in the role configuration or the entity-level sharing settings.
1. Feature not accessible
Each custom role defines granular permissions: view, create, edit, and delete access across projects, tasks, invoices, proposals, contracts, forms, files, contacts, time tracking, automations, and settings. If a feature isn't visible, the assigned role may not include view permission for that area. The workspace owner can check and adjust role permissions in Settings → User roles. Per-entity permissions can also override the role, so even if the role grants access, an individual entity may have restricted visibility applied to it.
2. Project not visible
Projects carry their own permission settings that control who can see and interact with them. If a project doesn't appear in the list, the project owner needs to add the team member's access directly on the project. Role-level permissions control whether projects as a feature are accessible, but project-level permissions control which specific projects are visible to each person.
3. Client can't see shared content
The client role is fixed and can't be customised. Clients only see the projects and entities they've been explicitly given access to, and everything outside that access stays hidden. If a client reports that something is missing, sharing the specific project or entity with the client from that entity's settings grants the necessary visibility. Within shared projects, clients can create and complete tasks, upload files, and start conversations, but features like scheduler, forms, and automations remain hidden from the client view.
4. Settings not visible
Certain settings pages are restricted to the workspace owner or to roles with settings permissions enabled. If a settings section doesn't appear in the main menu, the assigned role likely doesn't include access to that area. The workspace owner can grant settings permissions through Settings → User roles by enabling the relevant settings categories for the role in question.
