Loading...
Enterprise security & architecture
Connect enterprise sign-in and directory groups to the roles, business functions, and resources your teams need.
Discuss your architecture01Identity
Enterprise SSO and directory identity
02Membership
Active access to the selected workspace
03Role
What this membership may do
04Resource access
Approved content and connections
Successful sign-in is one step. Workspace membership and permissions determine what a person can do.
SSO & Active Directory
Use Microsoft Entra ID, formerly Azure Active Directory, for enterprise sign-in and directory provisioning. For hybrid Active Directory environments, review the Entra connection and group synchronization during deployment.
Connect the approved enterprise identity provider to the organization’s PlanAI workspace. Authentication follows the configured connection and the customer’s sign-in policies.
SCIM 2.0 provisions users and groups into PlanAI. Directory assignments map to workspace membership, privilege level, and business function.
Sign-in
Provisioning
Role-based access control
A role defines what a member may do. A business function selects the journey and the duty. It does not open or close a work module. Active membership binds the person to the selected workspace.
Membership in the selected company
Administrator, finance manager, member, or viewer
Selects the journey and the separation of duties
| Role | Work area | Typical permissions | Connection access |
|---|---|---|---|
| Enterprise administrator | Workspace administration | Manage membership, assignments, and enterprise settings | Configure permitted connections |
| Finance manager | Finance and shared modules | Work with financial plans and assigned resources | Access permitted finance integrations |
| Member | Shared work modules | Create and review work in the workspace | Use resources made available to the role |
| Viewer | Shared work modules | Read permitted content; no editing or administration | No integration administration |
This is an overview, not a grant of access. Module rules, resource permissions, and enabled connections determine the effective permissions.
Enterprise integrations
Plan learning, finance, and productivity connections around the data your team needs. Review each connection’s availability, permissions, and workspace assignment before activation.
Plan how course material and your internal learning catalog will support assigned learning paths.
CourseraCatalog planning
LinkedIn LearningCatalog planningDefine the financial records, accounts, and sync requirements needed for planning and analysis.
OraclePilot scoped
RampPilot scoped
QuickBooksRoadmapScope collaboration and business-system connections around approved teams, resources, and permissions.
Microsoft TeamsDeployment scoped
Microsoft OutlookScope review
SlackRoadmap
SalesforceRoadmapPilot and deployment connections require configuration and validation. Catalog planning, scope review, and roadmap entries are not generally available enterprise connectors. Confirm availability for your deployment. Third-party names do not imply endorsement.
Identify the administrator, approved permissions, and resources involved in the connection.
Confirm the company, directory, and business function that should receive access.
Test synchronization, failure handling, and access removal for the enabled connector.
Data & oversight
AI workflows can include prompts, business information, and selected document content. Review permitted sources, model services, and applicable data-use terms as part of deployment.
Selected authentication, security, integration, and content events are recorded. Directory reconciliation helps compare provisioned access with current membership. Agree on the events and review process required by your team.
Define storage location, encryption coverage, key management, and access requirements for the deployment. Confirm these settings in the technical review.
Agree on record, file, log, and backup retention; deletion handling; recovery arrangements; and incident contacts before rollout.
Compliance & certification disclaimer
PlanAI Inc. does not currently hold a SOC 2 certification or other formal third-party compliance attestations. The identity, access, integration, and data-handling practices described on this page outline configurable capabilities and architectural review topics. Customers should evaluate and validate specific security controls, hosting arrangements, and contractual data-processing requirements directly with the PlanAI team and their own IT, security, and compliance reviewers prior to deployment.
Architecture review
We can review your directory structure, permission model, required connections, and data policies with your IT and security teams.
Contact the PlanAI teamTo report a suspected vulnerability, contact the same team and request a secure way to share details.
