Your organization may need access to Stakeholder seats and custom roles. Contact your account team if these options do not appear in your settings.
How Stakeholder access works
A Stakeholder seat applies only inside the organization that assigned it.- It does not consume a Legal seat.
- It limits the member to permissions that support Stakeholder access.
- It takes priority inside that organization if the member has a Legal seat through another organization. Their Legal seat remains active elsewhere.
- If this is the member’s only organization, changing them from your Legal seat to a Stakeholder releases the Legal seat for another member. GC AI keeps the seat assigned when the member belongs to multiple organizations.
Available permissions
Stakeholder seats currently support these permissions:
Restricted Vault chat can find, filter, compare, summarize, and explain what the admitted documents say. It can also calculate arithmetic from stated values and compare dates and terms within the shared content. It reports contractual notice periods but leaves send-by dates for exercising contract rights to the member’s legal team.
Restricted Vault chat does not provide legal, financial, tax, accounting, investment, or commercial judgment. When a question asks for professional judgment, chat directs the member to the appropriate team and can still report the relevant document text. It also does not provide legal research, drafting, document editing, or access outside the shared Vault content.
Other permissions, including Main Chat, Projects, Skills, Playbooks, Automations, Company Profiles, Academy, the Word add-in, and Tasks, do not activate for a Stakeholder seat.
How roles affect Stakeholders
Roles define what a member can see and do. A Stakeholder can hold any assigned role, but only the Stakeholder-eligible permissions in that role activate. For example, a role may include Access shared Views, Restricted Vault chat, and Create projects. A Stakeholder receives the first two permissions. Create projects stays inactive because the Stakeholder seat does not support it. The built-in Standard access role grants a Stakeholder every permission in the table above. If a Stakeholder has no role, or only roles without eligible permissions, their roles grant no access and the Roles column shows No access. They can still open Views shared with them directly or through a group. To check a role, select View permissions in the member’s roles menu to see which permissions are eligible for their access and which are not. Roles granted directly and through user groups combine. Removing a direct role does not remove access inherited through a group.Assign a Stakeholder seat
Organization admins can assign Stakeholder access in several places:- Existing member: Open Settings → People, select the member’s badge in the Access column, and choose Convert to Stakeholder.
- Email invitation: Choose Stakeholder seat and the roles the person should receive when they join.
- Join request: Choose the person’s access and roles before approving the request.
- Automatic member access: For organizations with SSO or SCIM, in Settings → People → Settings, set the access and roles for future members who join through a shared link, Single Sign-On (SSO), or System for Cross-domain Identity Management (SCIM).