> 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.7-onboarding.md).

# Onboarding

Onboarding prepares your account and workspace so you can start useful work in Alludium.

The exact onboarding path can vary by account type, workspace state, role, and product rollout. Some users see a guided setup flow. Others enter a task-based setup experience that continues from the Inbox.

## Invited Member Onboarding

Most invited Members do not need to create or configure the workspace.

Member onboarding is usually focused on:

* Joining the correct workspace.
* Confirming account details.
* Reviewing the Inbox for starter or setup tasks.
* Opening relevant projects or deal rooms.
* Uploading or reviewing files when needed.
* Connecting personal accounts only when a workflow needs access on your behalf.

If a workflow needs personal connections, such as email, calendar, or CRM access, Alludium should ask that user to connect their own account rather than reusing another user's personal credentials.

## Owner Onboarding

Workspace Owners may be guided through broader setup for:

* Profile or role context
* Workspace information
* Workspace setup tasks
* Recommended integrations
* Starter agents, project setups, packs, or task types
* Trial, plan, or billing configuration where required
* People, roles, SSO, and governance settings where applicable

In the task-based experience, onboarding can start from a preparation screen and then continue as an onboarding task in the Inbox. This means setup work is tracked like other task work instead of living only in a one-time wizard.

## Workspace Setup Tasks

Some onboarding work appears as setup tasks. Setup tasks can guide you through:

* Choosing or confirming workspace context
* Connecting recommended integrations
* Activating project setups
* Completing pack-specific setup
* Reviewing required fields or readiness checks

When setup appears in the Inbox, treat it like other task work: open the task, review what is required, complete the relevant steps, and return to it later if needed.

## First Useful Actions

For Members:

1. Open **Inbox** and review active or starter tasks.
2. Open **Projects** if your work belongs to a durable initiative.
3. Open **Files** to upload or inspect source material.
4. Open **Settings** to manage your account, appearance, privacy, and notifications.

For Admins and Owners:

1. Confirm workspace settings and people access.
2. Review project setups, packs, and task types.
3. Configure required integrations and connections.
4. Configure agents, skills, templates, or automations where needed.
5. Confirm billing, SSO, and governance settings if you own those responsibilities.

## Troubleshooting Onboarding

If you land somewhere unexpected after signing in, check:

* Whether you are a Member, Admin, or Owner
* Whether onboarding is complete
* Whether there is an active setup task in the Inbox
* Whether your workspace needs billing or plan activation
* Whether required personal integrations still need to be connected
* Whether the docs page you are reading is meant for your role

If the setup task is blocked or missing, contact <support@alludium.ai>.


---

# 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.7-onboarding.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.