Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

As of July 2023

July 2023 help page: Invite people into Confluence

June 2022 steps:

Steps to adding a user are as follows:

  1. Find the email “attribute” of the user

  2. In Confluence Administration, User permissions, invite using that email address

  3. Ask IT to add user to uclason Confluence site.

  4. Have the new user complete a brief training (link; log on as “UCLA Health Employee Login”) and email a certificate of completion to the DGIT Service Assurance team

    • Alternatively, have the user complete the training, and attached the certificate to the ticket.

The DGIT group responsible is “DGIT Service Assurance”, so you can specify that in the ticket.

(Link to IT tickets)

Snapshots for June 2022 steps


Notes

The Active Directory may list a sonnet.ucla.edu or a mednet.ucla.edu as the email attribute, and it’s this attribute that needs to be linked to the user. Thus, even though sonnet.ucla.edu maps to mednet.ucla.edu (termed an alias), Confluence will only see the attribute when verifying the allowed email.

Confluence uses Atlassian accounts; Atlassian encompasses several software products, of which Confluence is one.

From Tony June 2022

The reason for the error is that Compliance has made it a requirement that we provide training to ensure that nobody is storing PHI on Atlassian Cloud, and that means unless we have a record of the completion of training, users are locked out of Atlassian Cloud. However, the training itself is in the middle of being updated, which puts us in this rather awkward situation. In the future, we will have better information on the error or on our websites about the necessity of the training to gain access.

I hope this helps. Thank you!


Service Assurance Lead Engineer
DGIT | Digital Technology
UCLA Health Information Technology

  • No labels