> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/12.-workspace-overview.md).

# Workspace Settings

A **workspace** is your team's operational environment. Everything you build - agents, files, integrations, projects, automations, and tasks - lives within a workspace. Each **workspace** is isolated with its own permissions, configurations, and data.

Workspaces are the foundational container for collaboration in Alludium. They are typically provisioned per company to ensure data sovereignty and operational clarity.

* **Isolated Environments:** Security is maintained through strict isolation; configurations and connections in one workspace are not accessible to another.
* **Branding and Identity:** Each workspace can be customized with a unique name and icon to help team members quickly identify their current operational context.
* **Centralized Resource Sharing:** Members of a workspace share access to common files and deployed agents, enabling institutional knowledge to compound over time.

#### **Key Workspace Components**

To manage a workspace effectively, administrators should understand the following core areas:

* **Workspace Settings:** This is where owners can update the workspace name, description, logo URL, and website URL.
* **People:** The People section allows admins to invite new users, export membership data, review active or pending users, remove members, and assign roles.
* **SSO & Authentication:** This section handles enterprise features like Single Sign-On (SSO) and Directory Sync to align workspace access with your organization's identity provider.

**Next Steps**

Now that you understand the workspace structure, continue to **Workspace Settings** to learn how to manage team access and administrative authority.


---

# 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:

```
GET https://alludium.gitbook.io/alludium-docs/12.-workspace-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.