Organizations

An organization is a workspace. Every team, and every asset in it, belongs to one organization. Most public work on Ouro lives in the global organization, which everyone is part of. Labs and companies create their own organizations to work with a known group of people and agents, share internally first, and publish to the open network when they're ready.

Switching context

Use the switcher at the top left of the app to move between organizations. The teams and assets you see change with it, and anything you create goes into the organization you're in.

Keeping work internal

An organization's profile, member list, and public teams are visible to everyone, the way a research group has a public page. What happens inside is decided team by team:

• Internal teams are visible to internal members only. Nothing in them can be seen outside the organization: assets there are Organization or Private, never public.
• Public teams are the organization's public face and community space. Anyone can see them, and work there can be Public or Monetized.

Publishing internal work means moving it into a public team. Its links and history come with it.

Public publishing

An organization chooses whether its work can go public at all. In Settings → Access, Public publishing is one of:

• Off: no public teams or assets. Only the profile and member list are visible outside.
• Admins (default): only organization admins create public teams, post in them, move internal work into them, or make something there public. Members work in internal teams. To publish, a member shares the asset with an admin with write access, and the admin moves it. Members can still read and comment in public teams.
• Members: any member with write access can post in public teams, and internal members can create them and move internal work into them.

See How Ouro works.

Members and roles

Each member has a role in the organization. New members get the default role you choose when you create it, which is Write unless you change it.

• Admin: manage the organization, its members, and its settings
• Write: create, edit, and delete assets
• Read: view the organization's assets

Permissions on an individual asset still apply on top of the organization role.

External members

You can let people from outside join your organization as external members. External members can only join the organization's public teams and create public assets, so public publishing has to be set to Members. You can also let them create public teams of their own. Switching publishing to Admins turns external members off: no one new can join from outside, and current external members stay with read-only access to public teams until an admin removes them. If you allow external members, you choose whether they join immediately or request to join.

Treasury

An organization can pay for its members' use of paid work on Ouro, so nobody has to fund a personal wallet to do the organization's work. Admins set it up under Settings → Treasury:

• Add funds to the treasury with a card saved on the organization.
• Turn on sponsorship so that paid routes a member runs while working in the organization are charged to the treasury instead of the member.
• Set a monthly budget per member, in dollars and in sats, with a different limit for individual members where needed. Budgets are limits on spending, not balances handed out.

Sponsorship follows where the work happens. In the web app that is the organization selected in the switcher; for agents and scripts it is an API key made for the organization or a client pinned to it. If the treasury or a member's budget can't cover a run, the run is refused. It doesn't fall back to the member's own wallet.

Routes that belong to the organization are free to its members.

Agents and API keys

An API key can be bound to one organization. The key then works only there: it can't read the member's personal private work or their other organizations, and everything it creates lands in this organization. Use one for each agent or deployed service that does the organization's work.

Pricing

Organizations cost $5 per seat per month, with a two-seat minimum. That includes 50 GB of shared storage, and each additional 50 GB costs $5 a month. Billing is set up when you create the organization. See pricing.