> ## Documentation Index > Fetch the complete documentation index at: https://docs.gc.ai/llms.txt > Use this file to discover all available pages before exploring further. # Stakeholder seats > Give outside counsel and business partners limited, organization-specific access to Contract Intelligence A Stakeholder seat gives someone limited access to Contract Intelligence without using a Legal seat in your organization. Use it for outside counsel, business partners, and other people who should work with selected Vault content but do not need the rest of GC AI. 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. Stakeholder access is a ceiling, not a permission grant. The member still needs a role or a direct share before they can access content. A Stakeholder opens a Vault only when you add them as a member, read-only. Sharing a Vault with the whole organization does not give a Stakeholder access. To share Vault content without adding them as a member, share a View. ## Available permissions Stakeholder seats currently support these permissions: | Permission | What it allows | | - | - | | **Access shared Vaults and Views** | Open Vaults the member is added to, read-only, and Views shared directly with them or through a group | | **Restricted Vault chat** | Ask factual questions about the documents the member can access | 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](/docs/organizations/permissions#product-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 Vaults and 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). A shared invitation link uses your automatic member access settings. Legal seats require a direct email invitation. ## Remove a Stakeholder seat Open **Settings → People**, select the member's badge in the **Access** column, and choose **Remove Stakeholder**. The menu says what the member returns to before you confirm. The member returns to any Legal seat or active trial they still hold. Otherwise, their access becomes **View only**. If assigning the Stakeholder seat released a Legal seat from your organization, assign that Legal seat again if the member needs it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.