-
Notifications
You must be signed in to change notification settings - Fork 50
New portal features #749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New portal features #749
Conversation
alex-yau-ttd
commented
Oct 31, 2024
- Ability to switch participants
- User Roles
- Audit Trail
- Ability to switch participants - User Roles - Audit Trail
docs/portal/audit-trail.md
Outdated
| @@ -0,0 +1,12 @@ | |||
| --- | |||
| title: Audit Trail | |||
| description: Set up and manage contacts for UID2 updates. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this is the same description from email contacts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch - fixed!
docs/portal/team-members.md
Outdated
| ## User Roles | ||
|
|
||
| Each team member is an administrator for the account, and can perform all activities relating to managing your team and your account, including the following: | ||
| Each team member has one of two user roles: Admin or Operations. Admins can perform all activities related to UID2 participation, as summarized in the [UID2 Portal Overview](portal-overview.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: probably "Admin users" instead of "Admins" makes sense here for consistency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep good call. done.
docs/portal/team-members.md
Outdated
| ## Edit Information for a Team Member | ||
|
|
||
| You can update any of the values: First Name, Last Name, Email, or Job Function. | ||
| Admins can update any of the values: First Name, Last Name, Email, Job Function, or Role. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: "Admin users" suggestion for here too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep good call. done.
docs/portal/team-members.md
Outdated
| The team member is added to the list, with Pending status, and an invitation email is sent to the invited person. | ||
|
|
||
| :::note | ||
| Team members can be added to more than one participant. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"can belong" instead of "can be added" sounds better to me. I think here would be helpful even though it is implied to add a sentence that explicitly connects this sentence with the participant switcher - like "if a team member belongs to more than one participant, they will be able to switch between participants as shown in the image"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept "can be added" because it is under the "Add a Team Member" section, but I've also made changes to use the "belong" terminology and connect it to the switcher.
|  | ||
|
|
||
| From the left sidebar, you can access the following pages relating to configuring your account: | ||
| Your participant name will be displayed at the top of the left sidebar. If your account has access to multiple participants, as shown in the example above, a dropdown menu will appear. You can use this menu to switch between participants in the portal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add somewhere like on the Team Members page an explicit sentence that explains how an account does get access to a new participant outside of their default one - that an Admin for a participant needs to add someone as one of the team members for that person to get access. Also this may be obvious, but when the admin adds them, they can add them with either Admin or Operations role to access to another participant - you can decide if it's obvious enough or not, I could go either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit hesitant to add details around how to invite an existing user to a new participant because it should just be the same as adding a brand new user to a participant. I'm planning on merging as-is and we can discuss/address separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alex-yau-ttd @ashleysmithTTD looking over these mods and I'd definitely be in favor of a) defining the roles in the doc (update: just found that in the next file!), b) explaining how someone is assigned a role. It should be covered, I think.
|
I noticed on the picture, the previous one has the name blacked out. Not sure if its for legal reasons, but maybe worth checking with someone, or just blacking out the name on the new picture you uploaded |
@ashleysmithTTD fair shout - I've just blacked out the name to err on the side of caution. |