> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/workspace-and-settings/members.md). # Members The Members tab shows every person in the workspace, their email address, and their role. Admins can invite new members, change roles, and remove members. All members can view the list and edit their own display name. ## Roles and permissions Filed has four workspace roles: | Role | Description | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Admin** | Full access to all settings including Appearance, SSO, and member management. Can invite, remove, and change the role of any other member. Cannot change their own role. | | **Level 1** | Standard member access. Can work with clients and binders assigned to them but cannot manage workspace settings or other members. | | **Level 2** | Standard member access, same scope as Level 1. | | **Level 3** | Standard member access, same scope as Level 1 and Level 2. | Level 1, Level 2, and Level 3 represent tiers within your firm's review workflow (for example, preparer, reviewer, and senior reviewer) rather than different permission boundaries. The sign-off system uses the distinction between them to track which stage a return has reached. When inviting a new member, the role defaults to Level 1. ## Inviting a member Only admins see the **Invite** button. The invite dialog collects three fields: **Name**, **Email**, and **Role**. After clicking **Send invite**, the member is added to the workspace immediately. **Important:** Filed does not send an email invitation to the new member. Teammates log in directly at [web.apps.filed.com](https://web.apps.filed.com) using email OTP (one-time password). You will need to share the URL and their login email with them directly. **Walkthrough: invite a member** 1. On the Members tab (admins only), click **Invite**. The Invite member dialog collects **Name**, **Email**, and **Role** (the role defaults to Level 1). ![The Invite member dialog with name, email, and role fields](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/members-invite/image1.webp) 2. Fill in the fields and click **Send invite**. A confirmation toast appears and the new member is added to the table immediately. ![A confirmation toast and the new member added to the table](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/members-invite/image2.webp) {% embed url="" %} ## Bulk inviting members The **Bulk invite** button (admin only) opens a dialog for adding multiple members at once. Use bulk invite when onboarding a large team rather than sending individual invites one at a time. **Walkthrough: bulk invite members** 1. Click **Bulk invite**. The dialog walks you through a template-based flow: download the template, fill in your team, then upload it. ![The Bulk invite dialog with download-template and upload-file actions](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/members-bulk-invite/image1.webp) 2. Click **Download template** to get a spreadsheet with **Name**, **Email**, and **Level** columns (Level can be Admin, Level 1, Level 2, or Level 3). Add one row per teammate, then click **Upload completed file** to add them all at once. The new members appear in the Members list. ## Changing a member's role Admins see a role selector dropdown on every row in the Members table. Selecting a new role updates it immediately, with no separate save step. The role selector on the admin's own row is disabled; an admin cannot change their own role from this page. Non-admin members see each member's role as a read-only badge. ## Editing your own name Every member can edit their own display name by clicking the pencil icon on their own row. A dialog opens with a **Name** field pre-filled with the current name; click **Save** to update it. Only the signed-in user can edit their own name; no other member's name is editable from this page. ## Removing a member Admins can remove a member by opening the three-dot menu on that member's row and selecting **Remove member**. A confirmation dialog states that the member will lose access immediately. Confirming the dialog removes them from the workspace. The remove option does not appear on the admin's own row. ## Pending and SSO-provisioned members There is no pending-invite state in Filed. A member is either in the workspace or not. Members who sign in through an enterprise SSO provider configured for the workspace are provisioned automatically on their first successful login, added with the default role configured on the SSO provider. No separate invite step is required for SSO users. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/workspace-and-settings/members.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.