Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Site contact needs to be the technical contact of a TCP ecosystem workspace |
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
...
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Site contact requires access to cloud products, such as ACFR, and Access Apps. To do this, they must be the technical contact for each of their site's Admin Center workspacesA Technical Contact can be set for individual workspaces, or at an organization level. This provides contact information to be used in messages that can appear in applications that participate in the Admin Center. |
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
You can use an email alias for these contacts as long as that email alias has a Workforce user in Users. For example, you could list a contact with the name IT Admins and an email alias that all your IT Admins subscribe to, so long as you have added IT Admins with that email as a user in Users |