Who created guest user
Currently i have no possibility to see who created a guest-user, except going through the audit-logs.
Maybe the User inviting the guest could be automatically set to the "Manager" attribute(which is currently not available for guest users).
Then the monthly review of created guest-accounts would be much easier to handle, as you could ask the inviter/manager if still needed.
This is good feedback and is in our backlog but not currently under development. While we work on prioritizing/designing the feature, it’s helpful to hear from you how you would use this information in your scenarios. Please let us know by adding comments here.
Trev Phillips commented
+1 from me for this, much needed!
Anu Rastogi commented
This is vital for auditing how many users are being created.
Craig Bellhouse commented
This is essential. When someone leaves our organisation, we need to see if they invited any guests before we delete their account. If they have, these need to be reviewed and possibly terminated as well. As someone else suggested, it needs to be a new attribute like invitedBy, not re-using an existing one for a new purpose.
Joakim Westin commented
This would be very helpful, please consider this!
Who deleted B2B account? I think this should be also asked. Isn't it?
I'm trying to know but don't see any helpful option here.
Nowadays it is a must to know who created the guest user account. Definitively to be developped !
Scott Egan commented
Yes, any hope of managing these properly requires some viability of who invited them.
We also need this for internal audits.
The second reason is to enrich the user attributes f.e. with phonenumber and company data to show them in the profile cards.
We try to recertify the guest accounts every now and then. This is done by sending out a generic mail which has limited effect. We would like to be able to send out a personalised mail e.g. "the following guest accounts you created show limited activity please let us know if these can be removed"
Due to the nature "fast adhoc communication with large intervals" of the work we do not want to simply remove all apparently stale guest accounts.
Hi I would be a natural feature to have as a API thing or an attribute on the guest object, like the Manager attribute on ordinary users.
I also believe this feature is required for internal auditing.
It would also be nice to know which content(s) a Guest User have access to.
Because of the lack of such feature, we must restrict the user who may invite Guest and also restrict Guest domain.
This could help us conform to internal auditing demands. Get's my vote.
Martin Wüthrich commented
this would be highly needed. but please do not set an existing attribute automatically. It would be great to have an additional attribute like "InvitedBy"
We are starting to use guest accounts and we are trying capture who created the accounts as well. Since we don't have a good way of doing this we're looking at restricting who can send invites via the 'guest inviter' role.