A knowledge base article about SPA: Direct Membership vs. Delegated Access provided by the UC Berkeley IT Service Hub - Knowledge Portal
|
Roles
|
Access
|
View
|
Services
|
Set up using SPA Admin tool
|
Purposes
|
|---|---|---|---|---|---|
| Direct Member | Full access and control of the associated bConnected account. | Can see all bConnected properties. | All services that accept a CalNet ID can potentially accept a SPA CalNet ID for authentication. | Yes, to create SPAs and manage membership, use the Special Purpose Accounts Admin App. | Can allow a CalNet ID to have multiple users that can share this SPA CalNet ID with others in their department for authentication purposes. Can anonymously send emails directly from the SPA-affiliated bMail account. |
| Delegated access role in bConnected | Limited Access to account. Cannot log in directly to the account and cannot give any access to others. | Has the ability to view the email account only within their personal bMail account from the pull down menu on the upper right hand side only. | bConnected via their personal bMail only. | No. | Can read and send emails from this account. Emails sent via delegated access show sender "SPA@berkeley.edu (sent by user@berkeley.edu). |
To create SPAs and manage membership, use the Special Purpose Accounts Admin App. SPAs are intended for collaboration and sharing. SPAs, their contents/data, and the shared email account are owned by the institution and the primary department (at the time the SPA is created) of the employee who creates the SPA.
If you have any questions regarding SPA CalNet IDs, contact itcsshelp@berkeley.edu.