> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/workspace-and-settings.md).

# Workspace & settings

A workspace is your firm's environment inside Filed, holding all your clients, team members, settings, and integrations in one place. Most accounting firms operate with a single workspace. If your practice spans separate offices or uses distinct tax-software configurations, you may belong to more than one, and you can switch between them from Firm Settings.

## Settings tabs at a glance

Reach Settings from the gear icon in the lower-left corner of the app. These tabs are available:

| Tab            | What it controls                                              | Who can see it                             |
| -------------- | ------------------------------------------------------------- | ------------------------------------------ |
| **Firm**       | Firm name, About description, workspace switching             | All members                                |
| **Appearance** | Logo, theme, fonts, colours, AI agent persona                 | All members (only admins can change it)    |
| **Access**     | Members, teams, client segments and access defaults           | All members (admin actions restricted)     |
| **Security**   | Enterprise single sign-on providers and session limits        | Admins only                                |
| **Binder**     | Default category and document order per return type           | All members                                |
| **Templates**  | Client intake templates, emails and questionnaires            | Admins only, when client intake is enabled |
| **Referrals**  | Your link for referring another firm to Filed                 | All members                                |
| **Developers** | Points to the Plugins page, where API keys are now managed    | Admins only                                |
| **Webhooks**   | Webhook endpoints, subscriptions, signing secrets and retries | Admins only                                |

In-app notifications (the bell icon) are available within the app.

## Admin vs. member access

Filed has four roles: Admin, Level 1, Level 2, and Level 3. Admins can do everything that Level 1-3 members can, plus:

* Add, remove, and change the roles of other members
* Create and delete teams, and change what each team is allowed to do
* Manage client segments and access defaults
* Configure SSO providers and session limits for the workspace
* Customise firm appearance (logo, theme, fonts, colours)
* Reset binder defaults

Members with Level 1, Level 2, or Level 3 roles do not see the Security, Templates, Developers or Webhooks tabs, or the Client segments and Access defaults tabs inside Access. They can open Appearance, but its settings are disabled with the note "Available for admins". If they reach an admin-only page directly, it shows a message that only admins can manage it.

Admins cannot change their own role from within the Members tab.

## In this section

* [**Firm settings**](https://docs.filed.com/reference/workspace-and-settings/firm-settings.md) - Update your firm name and description, switch between workspaces you belong to, or start a new workspace.
* [**Appearance**](https://docs.filed.com/reference/workspace-and-settings/appearance.md) - Upload a logo, choose a theme preset, set custom fonts and colours, and configure the AI agent's name and handle.
* [**Members**](https://docs.filed.com/reference/workspace-and-settings/members.md) - On the Access tab, invite team members individually or in bulk, assign roles, and remove members who no longer need access.
* [**Teams**](https://docs.filed.com/reference/workspace-and-settings/teams.md) - Group members into teams that decide which clients they see and which actions, like sending to tax software, they can take.
* [**Enterprise SSO**](https://docs.filed.com/reference/workspace-and-settings/sso.md) - Connect Filed to your identity provider using OIDC or SAML so your team signs in through your firm's existing credentials.
* [**Session limits**](https://docs.filed.com/reference/workspace-and-settings/session-limits.md) - Sign members out after a period of inactivity, and require them to sign in again after a set time.
* [**Binder settings**](https://docs.filed.com/reference/workspace-and-settings/binder-settings.md) - Define the default category and document order that new binders follow for each return type.
* [**Notifications**](https://docs.filed.com/reference/workspace-and-settings/notifications.md) - Read in-app notifications from the bell in the top navigation bar.

## Changelog

We ship new features and improvements to Filed every week. The changelog collects them in one place, newest first. Check back regularly to see what’s new. [View the changelog](https://filed.featurebase.app/changelog) (sign in with your Filed account).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.filed.com/reference/workspace-and-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
