> 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/readme/1.2-your-workspace-role.md).

# Your Workspace Role

What you see in Alludium depends on your workspace role.

The docs use **Member** as the default reader unless a page is clearly about setup, configuration, billing, or governance. That reflects the normal product split: most users do their work in Inbox, Projects, Files, and personal Settings, while Admins and Owners configure the workspace around them.

## Member

Members are the default day-to-day users of a workspace.

Members typically use:

* **Inbox** to create, continue, and complete tasks.
* **Projects** to work inside deal rooms, pipelines, campaigns, research spaces, or other durable initiatives.
* **Files** to upload, inspect, and use source material.
* **Settings** to manage account preferences and view workspace people.

Members may see project-specific shortcuts in the sidebar, such as a project type or deal-room category. If a workspace allows project creation, Members can create projects from the visible project controls.

Members usually do not configure the workspace-level building blocks behind the scenes. If you do not see Agent Builder, Skills, Integrations, Automations, Project Types, or Task Types in your sidebar, that is expected for a Member view.

## Admin

Admins manage much of the operational setup for a workspace.

Admins may configure or manage:

* Project and task operating surfaces
* Agents, templates, and skills
* Integrations, connections, and tools
* Automations and execution logs
* Workspace settings and people management

Exact access can vary by feature and workspace configuration. When a page is intended for Admins or Owners, the docs call that out.

## Owner

Owners have the broadest workspace responsibility.

Owners typically handle:

* Billing and plan management
* Workspace-level governance
* SSO and authentication setup where available
* Final control over people, roles, and workspace administration

Owners can also use the Admin configuration surfaces.

## Why The Split Matters

Alludium separates everyday work from workspace configuration so Members can focus on the work in front of them, while Admins and Owners maintain the reusable systems behind that work.

When you read the docs:

* Use the **Member** path for everyday task, project, and file workflows.
* Use **Administration** when you are configuring how the workspace works.
* Check **Roles and Permissions** if you need a deeper access model.


---

# 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/readme/1.2-your-workspace-role.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.