Overview
Before teams can protect revenue with Solvren, the workspace needs enough setup to make the first value visible.
The current setup journey is:
- Connect systems
- Choose what to protect
- Invite decision makers
- See the first risk or protected value
Advanced controls remain available for admins, but the first setup path should stay simple.
Step 1 - Create Your Organization
When you first sign in, you will be prompted to create an organization.
Provide:
- Organization name
- Primary administrator
- Default timezone
Organizations are the security boundary for data, approvals, and policies.
Step 2 - Connect Systems
Open Setup and connect the systems Solvren should watch first. Common starting points include:
- Stripe or billing systems
- Salesforce or HubSpot
- Jira or GitHub
- NetSuite or finance systems
- Snowflake, BigQuery, PostgreSQL, or MySQL
Setup health uses plain status language such as "Stripe connected", "Salesforce needs attention", or "Billing protection is active".
Step 3 - Choose What To Protect
Confirm which revenue workflows matter most:
- billing and invoices
- pricing and discounts
- lead routing
- renewals
- revenue recognition
- customer-impacting integrations
- operational automations
Solvren can start narrow and expand coverage over time.
Step 4 - Invite Your Team
Solvren works best when all stakeholders involved in revenue systems are included.
Typical stakeholders include:
- Engineering
- Finance
- Revenue Operations
- Product
- Analytics
- Risk or compliance
To invite users:
- Open Setup.
- Open Team & access.
- Click Invite user.
- Enter email addresses.
- Assign a role.
Users receive an email invitation. Each person can also set a display name and profile picture so owners and approvers are easier to recognize throughout the app.
Step 5 - Configure User Roles
Roles control what actions users can perform.
Owner
Full system access. Owners can configure organization settings, roles, license scope, and enterprise controls.
Admin
Operational administrators responsible for maintaining setup, users, integrations, policies, and security settings.
Submitter
Can create and submit changes.
Reviewer
Responsible for reviewing and approving changes.
Viewer
Can view permitted records without changing organization settings.
Step 6 - Configure Decision Rules
Decision rules determine which changes need approval and what proof is required. Admins can configure:
- approval roles
- approval mappings
- domain permissions
- attention routing
- evidence and proof expectations
Approval roles represent organizational responsibility, not just individuals. Examples include Finance, Engineering Lead, Product, Revenue Operations, and Security.
Users are assigned to these roles so Solvren can route approvals automatically.
Step 7 - Configure Security And Enterprise Controls
Enterprise setup may include:
- SSO
- restricted visibility
- customer-controlled support access
- write-back defaults
- license scope
- audit and diagnostics
Setup Complete
Once setup is complete, Home should show coverage health, Decisions should show any work needing action, Problems should show detected risks, and Proof should start building the value story.
Next: