Appearance
Understanding Roles & Permissions
Everything in Local Visibility Lab happens inside an Organization — your agency's workspace. Every person inside an organization has one of five team roles. The role decides what menus, buttons, and data they can see.
If you came here because the app is hiding something you expected to see, this page is the right place to start.
The five team roles
| Role | Who it's for | What they can do |
|---|---|---|
| Owner | The person (or people) who founded the org. There's always at least one. | Everything — including billing, closing the org, and managing other owners. |
| Admin | Senior staff you trust with operational control. | Everything except removing other owners. Can manage team, billing, settings. |
| Member | Day-to-day operators (account managers, content creators). | Manage profiles, posts, reviews, cases, contacts. Can be restricted to specific businesses (see below). Cannot manage team or billing. |
| Viewer | Read-only stakeholders (client liaisons, junior staff). | View profiles, reviews, reports, calendar. Can be restricted to specific businesses. Cannot edit anything. |
| Client Reviewer (UI label: "Client") | The end customer at the client business, when you give them limited dashboard access. | See only their own business's content; primarily used for approvals and report viewing. |
Provider Access (separate from team roles)
"Provider" is not one of the five team roles. It's a separate grant called Provider Access that lets an external service-provider organization work on a specific case in your workspace (e.g. a freelance designer or an outsourced SEO specialist). Provider Access is managed at the platform-admin level and is scoped per-case — the provider sees only the case(s) they've been granted access to, not your full org data.
Business scoping (member & viewer only)
Members and viewers can be scoped to a subset of businesses. Once scoped, they see only those businesses across every list, search, and report.
- A member scoped to Acme Plumbing sees Acme's profiles, reviews, and cases — nothing for your other clients.
- Owners and admins cannot be scoped (full access by definition).
- Changing a member's role to admin automatically removes their scoping.
Set scoping under Settings → Team → Edit Member. See Business Scoping for a deeper walkthrough.
What "end customer" looks like
If you're a small business owner whose agency uses Local Visibility Lab, you're typically not given a role at all. You don't sign into the agency's full workspace. Instead, you interact through:
- Magic links that drop you into a guided onboarding or approval flow.
- Public URLs (storefront, approval pages, photo upload, intake forms) that don't require any sign-in.
- A customer portal at
/my-casesand/my-billingif your agency turned that on for you.
Permission cheat-sheet
These are the permission keys used internally. You don't enter them directly — your role grants the right set automatically — but knowing them helps when a teammate asks "why can't I see X?"
| Permission | Owner | Admin | Member | Viewer | Client Reviewer |
|---|---|---|---|---|---|
profiles:view | yes | yes | yes (scoped) | yes (scoped) | own business only |
profiles:edit | yes | yes | yes (scoped) | — | — |
cases:manage | yes | yes | yes (scoped) | — | — |
contacts:manage | yes | yes | yes | — | — |
billing:manage | yes | yes | — | — | — |
team:manage | yes | yes | — | — | — |
org:close | yes (via support) | — | — | — | — |
Platform admin
A small number of people at Local Visibility Lab have platform admin access. The allowlist is configured server-side via the PLATFORM_ADMIN_USER_IDS env var on the API service (Clerk user IDs, comma-separated), gated by PLATFORM_ADMIN_ENFORCE=true. There is no flag on the user document — membership is checked against the env-var allowlist at request time. If you don't work at Local Visibility Lab, you will never see the /admin/* routes.
Next: Tour of the Dashboard