Organizations & Projects

Avi is organized as accounts → orgs → projects. You don't need to think about most of this day-to-day, but knowing the pieces helps when you collaborate or want to keep work separate.

Accounts

An account is the billing unit. When you sign up, you get a personal account automatically. You can stay on the free plan or upgrade to Pro — that choice lives on the account. See Billing.

Organizations (orgs)

An org is a workspace. Every account has one Personal org created at signup. You can also create or join shared orgs to collaborate.

  • Personal org — always yours, can't be renamed or deleted. Your personal projects live here by default.
  • Shared orgs — created by you or someone who invited you. Orgs have members with roles:
    • Owner — full control, including billing and member management.
    • Admin — can manage members and change settings. Can't manage billing.
    • Member — can be added to specific projects inside the org. Only sees projects they're a member of.

Org members can create shared projects. Project membership is explicit: the creator is added automatically, and other collaborators must be added directly.

Projects

A project is the container for a body of work: chat history, tasks, notes, files, skills, instructions. Every project has its own settings — its own tools enabled, its own agent instructions, its own conversation.

Personal projects

Every user in an org has a private project called Personal. Only you can see it, read from it, or chat in it — not even org owners or admins can. It's the right place for personal work inside a shared org (e.g. your own to-dos, your own notes) without worrying about other people seeing it.

You can create nested subprojects underneath your Personal project. These are also private to you.

Shared projects

Inside an org, any member can create shared projects. The creator is added as a project admin, and additional access is granted through explicit project membership.

Project modes

Each project is either:

  • Cloud — all files and tools run in the cloud. You can use it from any browser with no installation.
  • Local — files and tool execution happen on your registered device. Use this when the agent needs to touch code, files, or a terminal on your own machine.

You pick the mode when you create the project.

Per-project agent settings

Each project can have:

  • Instructions — persistent guidance the agent follows in this project. Good for domain-specific rules, style preferences, or constraints. ("Always respond in English." "This is a Node.js project using ESM." "Never touch the prod branch.")
  • Enabled modules — which bundles of tools the agent has access to. See Modules.
  • Tool permissions — individual tools can be turned off even if their module is enabled, for finer control.
  • AI model — override the org-level default. See AI Models.

Inviting teammates

From an org's settings, invite people by email. They receive a link that expires in 7 days. Accepting joins them to the org — you can also add them directly to specific projects during the invite. Each new org member gets their own private Personal project inside that org automatically.