> For the complete documentation index, see [llms.txt](https://docs.graspil.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graspil.com/en/app/projects.md).

# Projects and team access

If you're not the only one working with your bot — managers, marketers, analysts also need access — sooner or later you'll want a way to give them access to the right data without opening up your entire account.

That's what **projects** are for in Graspil.

### Why projects exist

A project groups several bots and channels together. Instead of granting access to each resource one by one, you add a teammate to the project once — and they get access to everything inside it.

* Combine multiple resources into a single project.
* Grant teammates access to the whole project with one invite.

{% hint style="info" %}
Working with projects and inviting teammates is a paid feature (in the plan comparison it's listed as "Collaborative work on the project"). On the free plan you work alone, without projects and without the ability to invite teammates.
{% endhint %}

### How it works: 3 steps

1. **Create a project.**\
   Go to **Settings → Projects** and click "**Create Project**". Give it a name — it's only for your own reference, in case you have several projects.
2. **Add the resources you need.**\
   Open the project and, in the "**Project resources**" block, pick the bots and/or channels your teammate should work with.
3. **Grant access to the project.**\
   Open "**Manage access**" → "**Grant access**", enter your teammate's email (or generate an invitation link without one), and select exactly what they're allowed to do.

Done — your teammate now has access to every resource in this project, without you having to configure access for each bot or report separately.

{% hint style="info" %}
A resource (bot or channel) can only belong to one project at a time. Adding it to a new project moves it out of the old one.
{% endhint %}

### What goes into a project

You add **bots and channels** directly to a project. Everything built on top of them — reports, broadcasts, automations, cohorts — becomes available to your teammate along with the bot itself, with no extra setup.

Resources that aren't added to any project are shown as "**No Project**" — only you, as the account owner, have access to them.

### How to invite a teammate

On the "Manage access" page, click "**Grant access**" and choose a method:

* **By email** — enter your teammate's email. If they don't have an account yet, the system creates an invitation: until they accept it, their access shows as "**Invite pending**".
* **Invitation link (no email)** — if you don't know your teammate's email, or it's easier to send the invite through a messenger, generate a link instead.

### What access you can grant

Access is granted section by section: you select "**Key permissions**" and decide exactly what your teammate is allowed to do — reports, base permissions, communications (chats and broadcasts), custom fields, integrations, Mini App, and more.

You can always see who has access to a project and what exactly they can do, and revoke access completely with "**Revoke all**".