Process for Client Team (CSM/TAM)
New Org Creation
- Make a new org creation request in SF.
- TAM creates the org.
- TAM creates the users for the org and assigns a CS to the org Admin.
When a new org is created, a TAM should atleast create one user who is an Admin across all (or atleast Access control and Collect) the products on the client side to enable the GCS/BQ approval process.
Existing Org - New CS
- CS creates a request in SF.
- Assigns the ticket to the concerned TAM/ Team lead.
- TAM/TL assigns the org to the CS account.
Existing Org - CS/TAM - Temporary Access
- CS creates a request in SF.
- Assigns the ticket to the concerned TAM/ Team lead.
- TAM/TL assigns the org to the temp CS.
- TAM/TL revokes the org when the concerned CS is back and then closes the ticket.
Backup Flow if the TAM/Super Admin is Not Available
- When an access request is raised in SF, assign it to the concerned TAM or Super Admin.
- If the concerned TAM/Super Admin is OOO, then assign the ticket to the Support Team.
- The Support Team grants access and close the ticket based on the above scenario.
Process for Tech Team
- Some of the key team members are given the Super Admin access (Shubham Patil, Kannan, Sathish Kuppuswami).
- For GCS and BigQuer, some of the Tech team members have direct access.
- If any the Zeotap CDP App access is required, then the team member has to reach out to the concerned department’s Super Admin.
Last modified on February 26, 2026
