---
title: "Organizations"
description: "How Ouro organizes people to enable collaboration."
date: "2025-07-14"
last_updated: "2025-07-14"
---

Users can operate in multiple contexts:

- **Personal context**: Your individual user space
- **Organizational context**: Scoped to a specific organization

When you switch contexts, the assets available to you will change.
When you create an asset, it is scoped to the context you are currently in.

<Callout type="info">
  Switch contexts using the switcher at the top left of the header.
</Callout>

### Creating and managing assets

- Assets are created in the active context
- Asset admins have full control over the asset
- Access options determine who can view the asset:
  - Public <span className="text-muted-foreground">— anyone on the platform</span>
  - Monetized <span className="text-muted-foreground">— anyone can discover, but payment is required for access</span>
  - Organization <span className="text-muted-foreground">— internal organization members only</span>
  - Private <span className="text-muted-foreground">— you and people you choose</span>

### Asset permissions

Users have role-based permissions on assets. Admins of assets can manage these permissions.

- **Admin**: Full access and management rights
- **Write**: Can create, edit, and delete assets
- **Read**: Read-only access to organization resources

## Organizations

Organizations group users and manage resource access.
Organizations create a private context where you can collaborate with a limited group of other members.

<div className="grid grid-cols-2 gap-8">
  <IconLink
    icon="organization"
    href="/settings/organizations/create"
    title="Create an organization"
    description="Set up a new organization"
  />
  <IconLink
    icon="settings"
    href="/settings/organizations"
    title="Manage organizations"
    description="View and manage your organizations"
  />
</div>

### Member roles

Within an organization, each member has a role. Individual [asset permissions](/docs/platform/organizations#asset-permissions) are still respected.
These roles determine how a user can use and manage assets within an organization.
By default, the creator of an organization will have an admin role, and all other added users will have write access.