Enterprise requirements
A plan your team can review.
Your proposal defines the controls, deliverables, and service commitments for your deployment. Confirm each requirement during scoping; inclusion and availability depend on the agreed solution.
- Single sign-on (SSO)
- Scope your identity provider, sign-in policy, and integration requirements. Confirm supported configuration and availability before rollout.
- Team accounts and admin controls
- Define team membership, administrator responsibilities, onboarding and offboarding, and who can manage workspaces and sharing.
- Usage limits and billing model
- Agree on analyst access, sample volume, concurrent workloads, storage, and analysis capacity. Document billing frequency, included usage, and how additional usage is handled.
- Data retention and deletion terms
- Document retention periods, deletion timelines, backup handling, and requirements at the end of the agreement. Review the standard retention policy as a starting point.
- Security review documents
- Request documentation of deployment boundaries, enabled capabilities, provider dependencies, and data handling. Agree on the review materials your security team needs. See our security overview.
- SLA and uptime commitments
- Agree on uptime targets, measurement, maintenance windows, exclusions, and remedies in writing. A service-level commitment applies only when included in your agreement.
- Private deployment or isolation options
- Choose hosted, dedicated managed, or on-premises deployment. Confirm the compute, storage, network, and tenant isolation boundaries for your environment.
- Audit logs and access controls
- Workspace roles and attributed activity support collaboration today. Scope required audit events, log retention and export, and administrative access controls for your deployment.
- Support response times
- Agree on support channels, coverage hours, severity levels, initial response targets, and escalation contacts. Record the response commitments in your proposal.