Workspace and project access
Workspace membership, roles and server-side checks govern what a person can see or change. Project visibility adds another boundary to the records in scope.
TRUST & SECURITY
Understand the controls behind the project record and the production questions to resolve with your team before rollout.
Workspace membership, roles and server-side checks govern what a person can see or change. Project visibility adds another boundary to the records in scope.
Built-in and custom roles support delegated responsibilities. Member and role administration is constrained by the acting person’s authority.
Audit records and project history provide context for reviewing changes, stage decisions and accountability.
AI GOVERNANCE
Organisation policies control AI availability and permitted data categories. Workspace allowances, optional project limits and usage reporting make consumption visible. Ari’s supported actions require confirmation and never replace gate or change approval.
Ari — PMO assistant
IDENTITY & CONNECTED SERVICES
Microsoft and Google sign-in depend on their configured admission rules. Integration credentials use a replacement workflow rather than a reveal control. Personal data consent is distinct from signing in.
A CLOSER LOOK
No. Available evidence depends on scope, user permissions and organisation policy. Stored answers can be withheld when access is narrowed.
No. Teams and Google Chat alerts point to a secure application link. Opening it still requires normal sign-in and workspace access.
Archiving closes access while preserving the workspace record. Authorised owners can reopen it. Production retention and contractual arrangements should be confirmed separately.
BRING THE WHOLE PICTURE INTO FOCUS
Explore AEVU around a real workflow your team needs to improve.