Organizations & members

Aquilla groups people and projects into organizations (orgs).

What an organization is

An organization is the scope for billing and for granting roles across more than one project. An org contains zero or more projects, and members: the people who belong to it.

Within an org, a member can hold an org-level role. At Maintainer and Owner, that org-level role grants the same access across every one of the org’s projects, which is handy when someone needs it on many projects at once. Below Maintainer (Viewer, Commenter, Reviewer, Contributor, Project lead), an org-level role by itself doesn’t open any project: those members still need to be added directly, through a team, or through project sharing to see one. Org-level grants use the same role ladder as projects.

Members and roles

People become members of a project (or an org) with a specific role that determines what they can do, from read-only viewing up to owning the project. Roles are explained in detail in Roles & permissions.

You add people to individual projects by inviting them (by email or with a shareable link) or, if they already share an org or project with you, by adding them directly; either way, they carry the role you choose.

Removing someone from a project

On a project’s Members page each person’s role shows as a plain label (Contributor, Maintainer, and so on) rather than an internal level number. To remove someone, choose Remove next to their name; Aquilla asks you to confirm first (“Remove member”). This only takes away the direct access you granted them; any access they still have through an org role, a team, or because they created the project is unaffected. To cut off every way someone can reach a project, use Revoke all: it lists each access path they hold (direct, org, team), then revokes them all after a typed confirmation.

Shared with you

If another organization shares one of its projects with you directly (without adding you to that whole org), those projects collect on a single Shared with you page, reachable from the sidebar. The sidebar link only appears when something is actually shared with you; each row shows the project, the org hosting it, and the role you hold there. If nothing has been shared with you, the page reads “Nothing shared with you yet.”

Clicking a guest organization in the org switcher takes you straight to that org’s own scoped Shared with you view: the same page, filtered to what that org has shared with you.

Inviting someone to the organization itself

Adding someone to a project is different from adding them to the organization. An org-level invite is owner-only: from the org’s Members page, an owner sends an invite (optionally by email; leave the email blank to get a shareable link instead) with an org role.

The recipient lands on a “Join {organization}” page showing who invited them and what role they’ll get: “Invited by {name} — you’ll join as {role}.” Accepting adds them as an org member with that role. A Maintainer or Owner role applies across every project in the org, not just one. A lower org role (Viewer through Project lead) makes them an org member but doesn’t by itself open any project; they’ll still need to be added to specific projects to see them.

Managing your org

Org settings, members, and per-project invites live in the Organization area, reachable from the sidebar. The Members page there is also where you add people to specific projects with the Add to projects button. What you can change depends on your org-level role.

An org’s sidebar splits into two views:

• Overview shows a dashboard at a glance: summary tiles for project count, average translated, validated, and audio percentage, and how many projects are stalled or overdue; a Projects table listing the org’s most recently updated projects (project, validated progress, status, and when it last updated), with a yellow warning icon marking any that need attention and a Show all {count} link if there are more than fit. Maintainers and owners can also show or hide two team-level sections (Team workload and Team usage) to the rest of the org, and maintainers and above see a Credits panel summarizing the org’s AI usage against its caps. That same spend also surfaces as a small credits dial in the AI agent panel: see Using the AI agent.
• Projects holds the full, searchable project table: every project in the org with its per-language progress, your role, activity status (“Not started” or “Stalled”), and any deadline, sortable by project manager (see Project Manager) and filterable by status. New project also lives here.

An org can also connect a Monday.com account and push project progress onto a board: see Monday.com integration.

Team settings

A team’s own page (Team → {name}) is tabbed: Projects, Members (with each member’s email, copyable), and an Overview tab still settling. A Maintainer or above sees a Settings icon next to the team’s name, which opens a dedicated page to rename the team or edit its description, both saved as soon as you leave the field, and a Danger zone with Delete team (“Delete ‘{team}’? This removes the team and all its grants.”), which asks you to confirm before it removes anything.

Restoring a deleted file

The org’s Archived page has two tabs: Projects (archived projects) and Recently deleted, which lists files deleted from any project in the org, including files whose project is itself archived. Each row shows the file, its project, and when it was deleted; choose Restore from its row menu to put it back. Restoring needs Project lead access or above on that file’s project; a lower role sees “Only project leads and above can restore a file.”

Note

Some org-level capabilities are still settling. The membership and role model described here is what your day-to-day collaboration is built on.