> ## Documentation Index > Fetch the complete documentation index at: https://docs.threetone.in/llms.txt > Use this file to discover all available pages before exploring further. # Members and access > Invite teammates, review workspace seats and groups, and understand how resource sharing differs from API-key permissions. Workspace membership gives a person access to your team in Threetone. Their seat, workspace permissions, and access to individual resources determine what they can do. Review each of these when adding or changing a member. Recording pending for Invite a member and review access. No playable video is available yet. ## Before you begin Confirm that you are in the correct workspace. To invite someone, you need permission to invite workspace members and an available seat of the selected type. Changing an existing member's seat or disabling their access requires workspace administration permission. Have the person's email address ready. If they need an existing group's access, identify that group before sending the invitation. ## Invite a member Open [Workspace > Members](https://threetone.in/app/workspace/members). Review the seat allocation and current members before creating another invitation. Select **Invite member** and enter the person's email address. Choose an available **Basic seat** or **Full seat**, then select any groups they should join. Submit the invitation, then check the pending invitations on the members page. The recipient must accept the invitation before it becomes an active membership. Confirm that the person appears in the members list with the intended seat. Review their groups and the resources they need to use. Screenshot pending for Members and access showing a synthetic invitation and separate seat and resource roles. This illustration is not a product screenshot. An invitation is not confirmation that the person has joined. If it is still pending, check the address and use the pending invitation's resend or cancellation action as appropriate. ## Understand the access controls | Control | What to review | | - | - | | Workspace seat | The members page labels seats as Admin, Full seat, or Basic seat. Choose a seat appropriate to the person's responsibilities and available allocation. | | Workspace permissions | Permissions govern actions such as inviting members, managing groups, or accessing product areas. Do not infer every permission from the seat label. | | Groups | Group membership lets you organize people and share resources with the group. Review membership when responsibilities change. | | Resource role | A shared resource can grant `admin`, `editor`, `commenter`, or `viewer` access to a person or group. This role applies to that resource. | | API-key permissions | An integration key has its own allowed API operations. Creating a key does not grant additional workspace authority to its owner. | Open [Workspace > Groups](https://threetone.in/app/workspace/groups) to review groups. You can create an application-managed group and manage its members. Some system or directory-managed groups have restricted controls. When using the [resource sharing API](/api-reference/workspace/share-workspace-resource), supply the resource type, role, and a user or group target. Setting `group_id` to `default` gives every workspace member that baseline role. Review this choice carefully before sharing sensitive resources. ## Change or disable a member's access On the members page, find the person and review their current seat before making a change. Confirm any administrator promotion or demotion in the dialog. Demoting your own administrator seat removes your administration access. Disabling a member and deleting their data are different actions. Permanent member deletion is not currently available from this page. The workspace owner's membership is protected from seat or access changes until ownership is transferred. ## Use the workspace API * [Invite user](/api-reference/workspace/invite-user) accepts `email` and optional `seat_type`, `group_ids`, and `usage_limit`. * [Invite multiple users](/api-reference/workspace/invite-multiple-users) requires a verified domain and an available seat for each accepted invitation. * [Update member](/api-reference/workspace/update-member) accepts the member's `email`, optional `is_locked`, and optional `workspace_seat_type`. * [List workspace groups](/api-reference/workspace/list-workspace-groups), [add a member to a group](/api-reference/workspace/add-member-to-user-group), and [remove a member from a group](/api-reference/workspace/remove-member-from-workspace-group) manage group membership. * [Share](/api-reference/workspace/share-workspace-resource) and [unshare](/api-reference/workspace/unshare-workspace-resource) change access to an individual resource. API seat values are `workspace_admin`, `workspace_member`, and `workspace_lite_member`. Use the endpoint's request schema rather than sending dashboard display labels. ## Troubleshooting * **A seat cannot be selected:** review the seat allocation. The invitation form disables seat types with no available allocation. * **An invitation is not accepted:** confirm the email address and check whether the invitation is still pending before resending it. * **A member cannot see a resource:** check their groups and the resource's sharing settings as well as their workspace membership. * **A member change is blocked:** check your administration permission and whether the target is the protected workspace owner or a directory-managed member. ## Frequently asked questions An invitation and an accepted membership are different states. Resource sharing and operation permissions must also be reviewed. Owner changes require the supported ownership-transfer process. The owner is protected from ordinary member-removal operations. No. Seat type describes membership; a resource role describes access to the shared resource. Do not infer one from the other. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.