
How do roles and permissions work in Revenue Proven?
Revenue Proven has two workspace roles: owner, who controls all settings and connections, and viewer, who can explore data and reports but cannot change account configuration.
Revenue Proven uses a two-role model within each workspace: owner and viewer. The owner controls all integrations and data flow that the whole team depends on, while viewers can read and analyze without being able to change anything structural.

Owner permissions
- Connect and disconnect LinkedIn Ads and CRM integrations
- Trigger manual syncs and configure sync schedules
- Manage billing and change subscription plans
- Invite and revoke team members
- Delete the account and all data
- Modify all workspace settings
Viewer permissions
- View all attribution dashboards and Company Insights
- Use Audience Explorer, Media Planning, and Ads Operations Suite in read mode
- Export data to CSV
- View Scheduled Reports and Competitor Intelligence analyses
- Cannot change connections, billing, or settings
Why this matters for influenced revenue
Revenue Proven connects LinkedIn Ads engagement to CRM revenue at the company level, so B2B teams can prove which campaigns influenced real pipeline and closed-won deals. When you are working with influenced revenue, the goal is always the same: tie marketing activity back to revenue you can defend in front of your leadership team.
Revenue Proven keeps the answer grounded in your own connected data. It pulls company-level engagement from the LinkedIn Ad Analytics API across five lookback windows (180, 90, 60, 30, and 7 days), matches those companies to HubSpot or Salesforce accounts by domain and name, and surfaces influenced pipeline and influenced revenue alongside a company-by-company journey timeline. That means the figures you see here reflect the accounts your campaigns actually reached, not estimates or modeled guesses.
If anything in this area looks unexpected, re-check that your LinkedIn Ads and CRM connections are active and that a recent sync has completed, then refresh the page.