Administrator and security setup

Establish an operating boundary, least-privilege access, healthy channels, and reviewable controls.

Expected outcome: Every member and connection has a clear purpose, risky access is minimized, and administrators can investigate change safely.

1. Configure the workspace so safe operation is the default
Security setup is not one screen. It is the relationship between people, roles, channels, customer data, sessions, and audit evidence.

2. Start with workspace health and required issues
Resolve broken connections, missing defaults, access anomalies, and readiness warnings before increasing customer volume.
Review point: A required issue can block an otherwise correct workflow

3. Separate ownership, configuration, and daily operation
Keep the Owner role limited. Give Administrators configuration responsibility and Members only the operating access they need.
Review point: Least privilege reduces both mistakes and investigation scope

4. Review team inbox membership and routing
A workspace role does not automatically mean every team should see every conversation. Align membership with operational responsibility.
Review point: Channel, inbox, and owner boundaries should agree

5. Keep personal mailbox content owner-scoped
Private Mail stays private by default. Share only the minimum context needed to create accountable team work.
Review point: Private email is not a shared team inbox

6. Require strong sign-in and review active sessions
Use MFA where available, remove unknown or stale sessions, and investigate unexpected geography, device, or timing.
Review point: Session review is part of offboarding and incident response

7. Use audit evidence for consequential configuration
Record who changed access, channels, privacy, billing, AI controls, and shared defaults—and verify the resulting state.
Review point: A saved setting is not verified until its effect is checked

8. Schedule recurring access and health reviews
Review members, invitations, roles, sessions, inbox membership, connected apps, channel health, and support evidence on a defined cadence.

This silent visual walkthrough was screen-recorded from the sanitized Acme Retail demo workspace. Follow the linked written guide for exact prerequisites, role boundaries, edge cases, and recovery.