All Help Articles

FAQ

How do team workspaces and seats work?

Team workspaces let multiple users collaborate in one Revenue Proven account, with the workspace owner controlling all data and invited members sharing access based on their role.

2 min read

Revenue Proven uses a virtual workspace model. One user owns the workspace and all the data within it. Additional team members can be invited to join that workspace and view the same dashboards, connection data, and reports without each needing their own separate LinkedIn or CRM connection.

Seat limits by plan

  • Free and Pro: owner only, no additional seats
  • Growth: up to 5 team seats
  • Scale: up to 10 team seats
  • Agency: up to 50 team seats
  • Enterprise: unlimited seats

How access works

All team members within a workspace see the same attribution data, synced to the workspace owner's LinkedIn Ads and CRM connections. Team members with viewer permissions can explore dashboards, run reports, and use Audience Explorer, but only the workspace owner can modify connections, trigger syncs, change billing, or adjust settings. If you are a member of multiple workspaces, you can switch between them using the workspace switcher in the sidebar.

Current help workflow

This answer was refreshed against the current Revenue Proven product and its exact /dashboard/settings/team route. It is written for the Shawn Brown demo workspace, whose pages contain real connected-system data in some areas and seeded examples in others.

Current product screen relevant to faq-team-workspaces-seats
Current product screen relevant to faq-team-workspaces-seats. Captured from /dashboard/settings/team.

Use this screenshot as the route-specific visual reference for “How do team workspaces and seats work?”. Labels, plan gates, roles, asynchronous loading, permissions, and available controls can vary with the signed-in workspace.

When troubleshooting, first confirm the active workspace, selected account, connections, date range and entitlement. Treat Save, Send, Sync, Publish, Resume, Reconnect and Delete controls as state-changing actions, and consult the current route before relying on older screenshots or navigation instructions.