Roles, access, and licenses
Check the workspace, role, project access, and feature license behind an unavailable action.
Check your selected workspace before requesting access. Your role, access to the work, and the workspace's active features all affect what you can open or change.
Check the role for the work
Sorena uses Reader, Contributor, Admin, and Owner roles. The role applies to the workspace, project, or team where it was granted.
| Role | Typical responsibility |
|---|---|
| Reader | Read the work available to that account. |
| Contributor | Add or change work where the feature permits it. |
| Admin | Manage the members and settings available at that level. |
| Owner | Manage ownership-sensitive actions as well as administration. |
A workspace role controls workspace actions, such as invitations. A project role controls its files and artifacts. Team membership can provide project access, and a project can share access with workspace members at a chosen default role. Ask a project Admin or Owner to check those grants when a project or edit control is missing. Workspace administration does not replace every project contribution requirement.
Creating a project needs workspace Contributor, Admin, or Owner access. Editing project work usually needs a project Contributor role or above; managing project members and settings needs project Admin or Owner access. Some actions also depend on the record's state, such as an approval or an active AI job.
Check the workspace's features
Open Workspace > Overview and read License snapshot. Check the status, time window, and Active feature access. Switching workspaces can change the features available to you.
| License | Customer features it covers |
|---|---|
| Platform | Core workspace, project, Drive, account, and usage access. |
| Assessment | Assessment artifacts, answer review, and policy analysis. |
| Autopilot Organizational Documents | Organizational-document artifacts and AI section generation. |
| Autopilot Timelines | Timeline artifacts and AI-assisted event generation. |
| Autopilot Contracts | Contract artifacts and AI contract workflows. |
| Integrated Management Systems | Management systems, requirements, linked content, and related catalogs. |
| Research Copilot | Research chats and Copilot tools, including opening research from other work. |
| Customer Support | Feedback requests, replies, and shared help requests. |
| Enterprise SSO | Workspace sign-in providers, provisioning views, and authentication-method controls. |
| Enterprise BYOAI | Workspace-managed AI provider credentials and configuration. |
Feature licenses apply alongside Platform. Opening an artifact can require its family license even when you have project access. An Ask Copilot action can also require Research Copilot. The Help landing page remains available with Platform; feedback-request tools have their own Customer Support requirement.
An assigned license can be pending or expired. Read its status and the explanation beside an unavailable action. A low-credit warning does not by itself mean that every feature is disabled; check the current credit and any action-specific message.
Days runway estimates how long the current credit would last at the previous seven days' average spend. The license window has its own expiry date; check both values when planning work.
Check limits and workspace status
The snapshot's Effective limits can show users, teams, projects, and storage. A limit can block a new invitation, project, team, or upload even when the feature is licensed. Workspace Admins and Owners can review Billing for credit, usage, and spend.
A workspace awaiting activation, suspended, or pending deletion can block access despite your membership. Ask a workspace Admin or Owner to check its status. Changing your project role will not resolve a blocked workspace.
Resolve an unavailable action
- Confirm the workspace and the record you intended to open.
- Read the message beside the disabled control or unavailable page.
- Check the feature in Workspace Overview, then the role for the relevant workspace, project, or team.
- If the feature and role are correct, check record locks, approval state, active jobs, and any limits reported by the action.
- Refresh after an access change. If the issue remains, contact support with the action, workspace name, and message shown.