Working with other people

A project doesn’t have to be just you and the agents. You can bring other people into it, so a project becomes a shared space — like a shared channel in a team chat. Everyone in it sees the same conversations, opens the same files, and can direct the same agents. It’s how a family or a small team runs work on one Lowkey together.

Sharing a project

Open a project’s settings and go to the Access tab — it lists everyone who can get into this project. To bring someone in, use Add people: search the roster by name or @handle, or just type their handle (@joy) and add them. They’ll see the project show up under Shared with me, where they can open its chats, files, and routines.

To take someone out, hit the ✕ next to their name. Access stops the moment you remove them.

Owner and members

Every project has one owner — usually whoever it belongs to — marked with a crown. Everyone else you add is a member. The difference is about managing access: only the owner (or an admin who runs the box) can add or remove people. Members do the work — chat, files, agents, routines — but they don’t change who else is in.

If you open the Access tab and can’t edit the list, that’s why: you’re a member here, not the owner.

Nested projects come along

Sharing follows the folder tree. When you share a project, every project nested inside it is shared too, with the same people. So sharing a parent folder is the quick way to hand someone a whole group of projects at once.

You’ll see this on the inside project as Inherited access — the people who got in through a parent, shown with a note like Shared via [parent]. You can’t add or remove them from the child; manage them on the parent project where the sharing actually lives.

Who gets pinged

Sharing a project doesn’t mean everyone is on the hook for everything. In a shared project, you’re pulled in for what’s addressed to you — when someone @mentions you, you get a notification; messages that aren’t aimed at you just sit in the thread for whoever’s interested. So a busy shared project stays quiet for you until your name comes up. See /notifications/ for how that lands.

Staying in control

Sharing hands real reach to the people you add, so it’s worth being deliberate:

• Everyone in a project sees all of it — its chats, its files, its routines. There’s no per-person wall inside a shared project.
• Agents act with the box’s full access. Anyone you share with can direct them, so only bring in people you’d trust with what’s on the box.
• Only the owner or an admin changes the list, and access ends the instant someone is removed.

What to read next

• Getting an agent’s attention vs. a person’s → /agents/
• What pings you and where they show up → /notifications/
• Who runs the box and adds the first people → /operator/provisioning/