How to identify the source of a Q.wiki user account?

Modified on Thu, 29 Jun 2023 at 10:18 AM

You need key user permissions to do the following steps.

What are the types of user provisioning? 

1. (Enterprise only) Active Directory import of users and groups. Here users and groups are imported from a defined path (can be set and changed by the service). The user administration takes place centrally in your AD. In Q.wiki itself these users and groups cannot be changed, deactivated or activated. 

The import of nested groups is possible.


2. Azure AD import of users and groups. Here, users and groups are imported from your Azure AD, which you have added in the provisioning of your Azure. The user management takes place centrally in your Azure. In Q.wiki itself, users and groups cannot be changed, deactivated or activated. 

Importing nested groups is not possible. 


3. local Q.wiki users. Users and groups are created directly in the user or group management of your Q.wiki. Users can be invited via their email address, and groups can be created and filled with active users. The administration of users can only be done by a KeyUser. Deactivating, activating, resetting password and changing email address can be done in Q.wiki by a KeyUser. 



And how do I identify them?

For Azure AD or AD: In the user management of Q.wiki, you can quickly see if a user was imported via your AD or Azure AD. 

To do this, click on the three dots menu for the user you want to manage. 

If the following text is displayed, the user was imported from your Azure AD or your AD. You cannot manage the user in Q.wiki, but only in your central infrastructure. Your internal IT can help you with this. 



For local users: If it is a local Q.wiki user, you will get the following selection in the three-point menu and have the option to manage the user.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article