Your team. The catalog. Same page.

Stop emailing files. Stop sharing logins. One workspace where editors process, reviewers approve, vendors upload, and stakeholders browse, without ever stepping on each other.

Core and Growth include unlimited internal workspace users
Vendor portal access, never a full seat
Enterprise OIDC SSO available
New roleStudio FreelancerActivity history
Capabilities
ViewUploadEditApprovePublish
Scope
Folder · /ProductsWorkspace
Conditions
Workspace member requiredProduct access scopeExpires in 30 days
Audit loglive
Granted "View"14:32:09
Granted "Upload"14:32:10
Granted "Edit"14:32:12
Scoped to /Products14:32:13
Verified workspace membership14:32:15
Applied product access scope14:32:16
Created role · Studio Freelancer14:32:18
Can edit 1,204 assets · cannot publish
Roles · product scopes · permission expiry

5

Permission levels. Set scope once, never debug who-can-do-what

0

Vendor-licence cost. Vendor portal seats are separate from your full seats

Unlimited

Internal workspace users on Core and Growth

Visible

Activity history for workspace review

The day-to-day, after Sirv.

The point isn't the role matrix, it's what the team stops doing and what they get back.

Stop emailing files around.

One workspace, one catalog. Vendors drop files into a portal, reviewers approve in-app, viewers grab what they need. The Slack-and-Dropbox shuffle is over.

Let stakeholders look without buying licences.

Core and Growth include unlimited internal workspace users. Marketers, merchandisers, and execs can browse and download without shared logins.

Onboard a new teammate in five minutes.

Invite by email, pick a role, scope to a brand or category, done. No security review meeting required because the role does the gating.

Know exactly who approved what.

Every approval, rejection, and publish is logged with the editor and timestamp. When a buyer asks 'why did this asset go live?' you have the answer in one click.

Review a mistaken approval cleanly.

Wrong file approved? Review visible Studio version history, choose the appropriate Studio original, and record what changed before publishing again.

Bake the team into your workflow.

Workflows respect roles. Editors trigger AI runs, reviewers approve, viewers get notified. Nobody can fire a workflow they shouldn't have access to.

Five roles. Pick once. Stop debating who can do what.

Each role is an opinion about a real person on your team. No 40-line permission spreadsheet. If you need finer control, scope a role to a brand, category, or product.

Admin

Owns the keys.

The person who pays the bill and answers when something breaks. Admins control billing, workspace settings, and who else gets a key.

  • Everything an editor can do
  • Billing and plan changes
  • Workspace settings and integrations
Manager

Runs the team.

Day-to-day owner of the workspace. Invites teammates, sets roles, and shapes how the catalog is organized, without touching billing.

  • Invite, remove, and reassign members
  • Manage roles and reviewer scopes
  • Create and curate collections
Editor

Does the work.

The catalog operator. Uploads, runs AI, fixes copy, ships approved assets to channels. The role most of your team will live in.

  • Upload, edit, and process assets
  • Run AI tools and workflows
  • Edit metadata, alt text, and tags
Contributor

Uploads safely.

Photographers, vendors, and partners who add files but don't run AI ops or change copy. Scope them to their products and stop worrying.

  • Upload assets
  • Add to collections
  • Add tags
Viewer

Browses and grabs.

Merchandisers, marketers, sales, and stakeholders who need to find files, not edit them. Core and Growth include unlimited internal workspace users.

  • Browse and search the catalog
  • Download approved assets
  • Watch shared collections

Three ways to add a person, only one costs a full seat.

Most teams overpay because they treat every collaborator like an editor. We don't. Stakeholders get viewer seats. Vendors get a portal. Editors get the full thing.

Full seat

For people who edit, run AI, and ship.

  • Full access by role (Admin / Manager / Editor / Contributor)
  • Counts against your plan's full-seat allotment
  • Can run AI ops and consume credits

Internal workspace user

For teammates who browse, review, or edit by role.

  • Search, preview, and download approved assets
  • Unlimited on Core and Growth; Enterprise custom
  • Role-based browse and download restrictions

Vendor portal access

For suppliers, photographers, and partners.

  • Scoped to specific products, brands, categories, or tags
  • Never counts against your full-seat allotment
  • Sees only the vendor portal, never your dashboard

What your team does in here.

One workspace per brand or client.

Agencies and multi-brand teams keep clients fully isolated. Each workspace has its own assets, members, billing, and audit trail. Switch in one click.

  • Clients never see each other's files
  • Per-workspace billing for clean chargebacks
  • Workspace-scoped roles. Managers don't bleed across

Invite the right people in the right way.

Three invite modes: full-seat editors, viewer seats for stakeholders, and a separate vendor portal for suppliers. Each has its own login experience and price.

  • Email invites with role pre-selected
  • Core and Growth include unlimited internal workspace users
  • Vendor portal access. Never counted as a full seat

Watch the room without the noise.

Real-time activity surfaces uploads, approvals, AI runs, and edits in one feed. Filter by member or asset to see exactly who's doing what right now.

  • Live activity feed across the workspace
  • Per-asset history. Every edit, every approver
  • Review visible workspace activity

In-house or vendor-led, the team model fits both.

Most teams run one of these. Some run both at once. The roles, scoping, and audit log hold either way without a redesign.

In-house catalog ops

Your team owns the catalog end-to-end. Editors process, managers review, the workspace is the source of truth.

  1. 1Editors upload and run AI ops
  2. 2Managers spot-check and approve in batch
  3. 3Approved assets push to Shopify and CDN
  4. 4Viewer seats let stakeholders grab approved files

Vendor + reviewer split

Vendors and external photographers feed the catalog through a scoped portal. Your reviewers handle exceptions. Clean uploads sail through.

  1. 1Vendors drop files into their scoped portal (no full-seat cost)
  2. 2Validation auto-fixes the small stuff
  3. 3Reviewer queue handles edge cases, assigned by category, brand, or product
  4. 4Approved assets publish. Rejected ones get a clean reason and can be resubmitted

The questions team leads keep asking.

What's the difference between a full seat, a viewer seat, and vendor portal access?

Internal workspace users edit, review, browse, or download according to their role. Core and Growth include unlimited internal workspace users; Enterprise is custom. Vendor portal access is separate for suppliers and photographers, scoped to specific products, and never exposes your dashboard.

Can a person work across multiple workspaces with different roles?

Yes. Roles are per-workspace, so the same person can be an Admin in your apparel brand workspace and a Viewer in your home goods workspace. Switching workspaces is one click in the top bar.

How do approvals work? Can a reviewer approve anything?

Reviewer scope is configurable. You can grant approval rights for a specific product, a category, a brand, a tag, or the whole catalog. A reviewer assigned to 'Outdoor' can't accidentally approve apparel.

What happens to an editor's work when they leave the team?

Their assets, approvals, and edit history stay attached to the audit log under their previous identity. You revoke their seat with one click and their access dies. Nothing they uploaded or approved disappears.

Do you support Enterprise SSO?

Enterprise OIDC SSO is available with scoped admin roles, custom retention windows, and a signed DPA.

Can I see who approved or published an asset months later?

Yes. Every approval, rejection, replacement, and publish is logged with the member and timestamp. Visible version history follows the current Free, Core, Growth, or custom Enterprise packaging.

Can vendors trigger workflows or just upload files?

Vendors upload files today. Vendor-originated workflow triggers are planned, and they will only resolve products and assets inside that vendor's grant.

How are paid plans gated: by seats, by features, or both?

Free includes one workspace-owner seat. Core and Growth include unlimited internal workspace users, with role-based product access. Enterprise packaging is custom and can include Enterprise OIDC SSO.

Approval workflows, formalized.

Multi-stage routing, design ▸ legal ▸ commercial ▸ live, with parallel approvers, scoped reviewers, and SLAs per stage. Reviewer-only seats already exist. The routing UI is next.

Related reading

Where to go next, depending on which side of the team setup you're tackling first.

Vendor portal & supplier access
Workflows that respect roles
DAM the team works inside
Agencies running 10+ clients

Core and Growth include unlimited internal workspace users. Growth ($499/mo) adds supplier workflows, while Enterprise offers custom packaging and Enterprise OIDC SSO.

Bring the whole team in, without the licence sticker shock.

Editors run the catalog. Viewers grab approved files. Vendors stay scoped. One workspace, one bill, one audit trail.

25 free credits to start. No credit card required.