Organizations & Projects
Multi-tenant hierarchy in Vizco — organizations, users, roles, and projects.
Vizco uses a multi-tenant hierarchy where organizations own projects, and projects contain all your assets, folders, widgets, and API keys.
Organizations
An organization is the top-level account in Vizco. When you register, an organization is created automatically with you as the owner.
Each organization has:
- A unique name displayed in the dashboard
- A unique slug used in URLs
- One or more users with different roles
User roles
| Role | Permissions |
|---|---|
| OWNER | Full access. Can manage users, billing, and all resources. |
| ADMIN | Can manage projects, assets, and widgets. Cannot manage billing. |
| MEMBER | Can view and edit assets within assigned projects. |
Projects
Projects are containers within an organization that group related resources together. A typical setup might have one project per app or per client.
Each project has:
- A name for display
- A unique slug within the organization
- Its own set of assets, folders, widgets, and API keys
Example structure
My Company (organization)
├── Mobile App (project)
│ ├── Assets: hero.jpg, logo.png, banner.jpg
│ ├── Folders: Hero Banners, Product Images
│ ├── Widgets: hero-carousel, product-grid
│ └── API Keys: android-app-key, ios-app-key
└── Website (project)
├── Assets: about-team.jpg, office.jpg
├── Folders: Team Photos
├── Widgets: team-gallery
└── API Keys: web-key
API keys are scoped to a single project. A key created for "Mobile App" cannot access widgets in "Website".
Managing organizations
/api/organizations/{orgId}JWT/api/organizations/{orgId}JWTManaging projects
/api/organizations/{orgId}/projectsJWT/api/organizations/{orgId}/projectsJWT/api/projects/{projectId}JWT/api/projects/{projectId}JWT/api/projects/{projectId}JWTSee the full API reference for request and response details.