Studio & agency workflow
Provisioning multi-tenant workspaces, granular role-based access frameworks, and inline editorial review tracks to coordinate collaborative asset publishing across distributed agency teams.
Architectural alignment
Studios and agencies need one workspace with many hands—producers, photographers, retouchers, and client-facing managers—without sharing a single password. ArtInStack uses the team module for Projects (internal file review and delivery rails) and role-scoped dashboard access: owners and managers handle billing and Settings; creative roles work in Pages, Posts, Portfolio, and Media; project-scoped staff see only assigned Projects. Client-facing proofing still flows through Portal Manager and Products, so retainers do not sprawl across email threads.
Required module configuration
| Area | Why you need it | Notes |
|---|---|---|
| Team module | Invites, roles, scopes | Required for multi-user studio |
| Projects | Internal review, pinned assets, delivery | Not the same as Portfolio marketing galleries |
| Portal Manager | Client rooms and entitlements | Studio/agency client delivery |
| Pages / Posts | Multi-author publishing | Posts for authors with limited scope |
| Media + Portfolio | Shared asset spine | Cross-brand libraries per workspace |
| Products | Client upsells and print | Optional per account |
Roles such as manager, creative director, agency photographer, editor, and assistant map to different sidebar visibility—assign the least access that still lets the person finish their job.
Step-by-step implementation blueprint
- Settings → Team — Invite your producer or ops lead as manager; invite creatives with project or global scope as appropriate.
- Projects — Create a client project folder; upload work-in-progress assets for internal review.
- Portfolio — Keep client-facing galleries separate from internal project bins.
- Portal Manager — Configure default widgets; send a test Invite Client for an active engagement.
- Pages — Restrict who can publish: only owner / manager / designated roles should hit Publish.
- Posts — If the studio runs a journal, add an author who can access Posts and Media only.
- Document internally which brands share one workspace vs separate photographer accounts (separate workspaces remain the cleanest cross-brand isolation).
- Run a dry-run client delivery from project upload → portal invite → client view.
Verification framework
- Each teammate sees only the sidebar items their role allows.
- Project-scoped user cannot open billing or unrelated client projects.
- Internal Projects files are not accidentally exposed on a public Portfolio URL.
- Client portal invite opens with correct gallery or download entitlements.
- Published site changes trace to the intended author account.