> ## Documentation Index
> Fetch the complete documentation index at: https://getligura.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Work with your team

> Keep shared context, invite teammates, and understand who can do what.

A teammate should be able to pick up useful research without asking you to reconstruct the whole conversation. In Ligura, you can keep that research, the current plan, and the remaining tasks in a shared Work.

Team and sharing controls depend on your access and the features available in your deployment. If a control described here is missing, ask your team owner or [contact support](mailto:support@getligura.com).

## Keep personal and team work in the right place

Your personal workspace and a team's workspace are separate. Creating or joining a team does not move your personal Works into it. Check the workspace selector before creating a Work or asking an AI to save something.

To start a team, open **Settings**, choose **Teams**, and create a team with a name. Ligura creates its workspace and makes you the owner. Use the workspace selector to return to personal work or switch teams.

Inside the team workspace, create a Work for a meaningful project such as **Elephas Teams Launch**. An optional Group such as **Elephas** can keep related Works together. Groups organize Works; group-wide sharing is not currently available.

## Invite a teammate

Owners and admins can manage invitations from the **Team** page.

1. Open **Invitations** and enter the person's email address.
2. Choose their workspace access. A Viewer can read, an Editor can change content, and a Manager can also share and change access.
3. Create the invitation, then copy the link while it is displayed.
4. Send the link to the person yourself. Ligura does not email team invitations.
5. The recipient opens the link, signs in with the invited email address, and accepts.

Invitation links expire after seven days and are shown only when created. If you lose one, get a new link from **Invitations**. The old link then stops working. You can also revoke a pending invitation.

## Understand roles and access

There are two different questions: who runs the team, and what someone can do in its workspace.

| Team role | What it means |
| - | - |
| Owner | Runs the team, including members, roles, admins, and owners. Can delete the team. |
| Admin | Manages members and access, but cannot manage owners or admins. |
| Member | Belongs to the team and sees the content they have access to. |
| Guest | Someone outside the team with access to specific shared items. |

Workspace access is shown separately as **Viewer**, **Editor**, or **Manager**. Being listed as a team member does not by itself mean someone has access to every Work. Check their workspace role and the Work's **Access** panel.

A Work that is **Open to the workspace** is visible to everyone with a role in that workspace. A **Restricted** Work is for named people, with access retained by team owners and admins. Restriction does not hide content from those administrators.

## Continue together

Here is an illustrative launch workflow:

1. Sarah saves customer research as a Page and comparisons as a Table.
2. John reads that context, improves the recommendation, and updates the current plan.
3. Maya uses the saved material for the launch presentation and records what remains unresolved.

Keep a short current State and clear next Tasks so the next person knows where to begin. Assigning an owner to a task describes responsibility; it does not grant that person access or send a notification. Team work remains with the team when a contributor leaves.

Each person uses their own authorized AI connection. Name the team workspace and Work in your request:

> In the Elephas team workspace, read the current State and plan for Elephas Teams Launch. Help me prepare the next launch task.

An AI needs both a suitable connection and permission to use that shared content. Human access alone does not guarantee AI access. Review **Let them use it with their AI apps** when sharing.

For access to just one Work or saved item, follow [sharing and invitation links](/docs/sharing-and-links.md). For a session-by-session walkthrough, see [continue your work](/docs/continue-your-work.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.