Getting started
Environment setup, business unit configuration, user provisioning, and the 30-day implementation sequence.
- Implementation overview
- Provisioning users and roles
- Configuring your first business unit
Documentation
Everything needed to implement and operate Vector
Written for revenue operations leads, administrators, and integration engineers. Article stubs below outline the documentation structure.
Reference
Documentation sections
Object model
Accounts, sites, assets, bids, quote revisions, projects, change orders, agreements, and how they relate.
- Account and site hierarchy
- Quote revision lifecycle
- Change order objects
Atlas AI configuration
Signal selection, model tuning per business unit, action queue routing, and reviewing recommendation history.
- Signal reference
- Tuning award probability
- Auditing recommendations
Integrations
ERP order book sync, estimating imports, field service connectors, and warehouse exports.
- ERP sync setup
- Estimating import mapping
- Warehouse export schema
API reference
REST endpoints, authentication, pagination, rate limits, and event webhooks.
- Authentication
- Accounts endpoints
- Webhook events
Security and governance
Role-scoped access, audit exports, SSO and SCIM, and data handling for AI features.
- Roles and permissions
- SSO and SCIM
- AI data handling
Implementation support is included with every agreement. A revenue engineer walks your team through configuration, migration, and Atlas AI tuning.
Talk to an engineerRelated