> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/administration/workspaces.md). # Workspaces A workspace is where your organization's maps, data, and members live. Start a new one, change its settings, or hand it over. A workspace is your organization's shared home in Felt: its maps, projects, data sources, and members all live there. You can belong to several workspaces, and each one has its own plan, seats, and billing. Click your workspace name in the sidebar to switch between them or create a new one. {% embed url="" %} ## Create a workspace Anyone with a Felt account can create a workspace. You become its admin. Your first workspace starts with a 7-day trial of the Business plan and the Platform add-on. A workspace you create after that starts on the Free plan. See [Billing](/plans-and-billing/billing.md). 1. Click your workspace name in the sidebar to open the workspace menu. 2. Open **Switch workspace**. 3. Click **Create workspace**. 4. Enter a name for the workspace. 5. Optional: Enter your coworkers' email addresses to invite them. To switch workspaces, select one from **Switch workspace**. See [Account and login](/getting-started/account-and-login.md#open-the-right-workspace). ## Workspace settings Click your workspace name in the sidebar, then click **Workspace settings**. Settings are grouped into the Members, Usage, Billing, Developers, and Workspace tabs. Only admins see Usage and Billing. The Developers tab, for API tokens and webhooks, appears for people with Admin or Edit access to the workspace. Admins can also change the workspace's name and icon on the Workspace tab.
Workspace tab of Workspace settings, with the Basics, Map sharing, Hosting region, Joining the workspace, and Enterprise SSO sections.
### Enterprise settings {% hint style="success" %} Available on the Enterprise plan. [Talk to sales](https://felt.com/sales) {% endhint %} On Enterprise workspaces, the Workspace tab has these extra sections, and only admins can change them: * Map sharing: the public link access that new maps, including drafts, start with. Existing maps don't change. * Hosting region: where Felt stores the workspace's data. See [Regional hosting](/administration/regional-hosting.md). * Joining the workspace: lets people with your company's email domain join at sign-up, with the access you choose. * Enterprise SSO: login through your identity provider. See [SSO](/administration/sso.md). ## Custom branding {% hint style="success" %} Available on the Enterprise plan. [Talk to sales](https://felt.com/sales) {% endhint %} Custom branding is a package you arrange with Felt's sales team. Once it's set up, an admin finds its two settings in the **Branding** section of the **Workspace** tab in workspace settings: * Brand color: the selection and highlight color on every map in the workspace. * Hide the Felt logo in embeds: removes the Felt logo from embedded maps. Custom branding doesn't change fonts or add logos to maps. To set a highlight color for an individual layer, use the `highlightColor` property in Felt Style Language (FSL). It overrides the brand color for that layer. See [Advanced styling (FSL)](/styling/advanced-styling-fsl.md). ## Leave a workspace After you leave a workspace, you need a new invitation to return. On a paid plan, maps and data sources you own move to the workspace admin who most recently opened the workspace, and your drafts move to them in a new private project named for you. See [Manage members](/administration/manage-members.md#keep-a-departing-members-maps-and-data). {% hint style="danger" %} On the Free plan, leaving deletes your drafts. Move any drafts you want to keep into a shared project before leaving. Content in shared projects stays. {% endhint %} 1. Open workspace settings, then click the **Workspace** tab. 2. In the **Remove** section, click **Leave workspace**. 3. Click **Leave** to confirm. If you're the workspace's only admin, you can't leave. To hand a workspace over, [give another member Admin access](/administration/manage-members.md#grant-or-remove-admin-access), then leave. To hand over one map, give the other person Edit access, or move it into a project they can edit. ## Delete a workspace To delete a workspace, you need Admin access. {% hint style="danger" %} Deleting a workspace permanently deletes all its maps and cancels its plan or trial. Links to its maps and embedded maps stop working. You can't undo it. {% endhint %} 1. Open workspace settings, then click the **Workspace** tab. 2. In the **Remove** section, click **Delete workspace**. 3. Enter `DELETE`. 4. Click **Delete workspace**. ## Workspace terms | Term | What it means | | --------------- | ------------------------------------------------------------------------------------------------------------------------------- | | Project | A group of maps in the workspace, open to the workspace or private. See [Organize maps](/maps/organize-maps.md). | | Drafts | Your own maps that aren't in a project yet. See [Organize maps](/maps/organize-maps.md). | | Member | Anyone added to the workspace. See [Manage members](/administration/manage-members.md). | | Seat and viewer | A seat lets someone do the work; a viewer views and comments. See [Seats and viewers](/plans-and-billing/seats-and-viewers.md). | | Access | What one person can do on a map, project, data source, or the workspace. See [Permissions](/administration/permissions.md). | | Admin | Someone with Admin access to the workspace, who manages members, billing, and settings. | --- # 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://help.felt.com/administration/workspaces.md?ask=&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.