IAM manages access across Atlas
Without IAM, access is defined by implementation- not by design
User IAM Applications
Core Planning
Target Options
Manager
Manager
Disney Ads Agent
Inventory Catalog
Manager
Access Control Layer
Atlas
Manager
Define once. Scale everywhere.
- Define roles and permissions once
- Apply access consistently across applications
- Govern access centrally across Atlas
IAM
Single source of truth for access
Atlas
Core Planning
Target Options
Manager
Manager
Disney Ads Agent
Inventory Catalog
Manager
Manager
We structure access in 3 layers
Planner
Core Planning → Edit
TOM→ View
ICM→ No Access
Ad Operations
User RoleApplication + Permissions
- Users do not directly get permissions
- Roles abstract access
Define roles before designing access
Roles define what users can access and do across Atlas applications
Role
What they can do
Primary Access
Planner
Core Planning
Create and edit plans
Specialist
Review, validate, approve
Core Planning + TOM
Ad Ops
ICM
Manage inventory setup
Admin
IAM / Admin
Full Access
*Role definitions for first release are still being finalize
Separate mental models to reduce complexity
User Management → who has access
Role & Permissions → what access means
Demo order:
- User Management - who has access
- Add/Edit User - assigning role/app access
- Roles & Permissions - what access means
- Create/Edit Role - defining role permissions