Translations by Ralf Hilgenstock

The section *Personal user tokens* displays all the tokens that you have generated for individual users and whether they have been accessed or not amongst others.

**Service**: Choose the service group from the drop-down list for which you want to enable the token. Only services that allow user token access can be chosen.

**Protocol**: Select the web services protocol that is associated with the user. You can only see the protocols that are enabled.

**Auth type**: Choose the type of authentication that you selected for the user. The options are:

Even if you use Mahara with one organisation only and do not want to distinguish different departments within your organisation, we recommend you set up at least one institution and not use "No institution". By setting up at least one institution you will have two more roles available: institution staff and institution administrator.

You can create institution administrator accounts which are less powerful than the site administrator accounts. By having institution administrators, you can allow them to take care of user account creation and group creation etc. without giving them full powers over the site preventing that too many people can make site changes.

**Last name**: Displays the last name of the user.

The profile picture of the user is displayed.

**Username**: Clicking on the username, you are taken to the user's administration settings page instead of their profile page as you would with the other names.

**Display name**: Shows the display name of the user.

**First name**: Displays the first name of the user. This is the default column for sorting results.

Regenerate clean URLs for existing users in bulk

This feature allows you as site administrator to specify the base URLs for media that you want your users to be able to embed. These iframes are then considered safe and will not be stripped out of a *Text* or *Note* block, the *External media* block or a journal entry where you can use them. You do not have to write bespoke filters for using these iframe sources.

**Quota notification threshold**: :index:`You <single: Quota notification threshold>` can set a percentage for when a user receives a notification about reaching the upload limit for files. They can then decide to delete files to free up space or contact the site or institution administrator to check if they can receive more space.

**Height**: Choose the maximum height (in pixels) of the profile pictures for users.

**Width**: Choose the maximum width (in pixels) of the profile pictures for users.

Turn on the option **Convert "Note" blocks** to convert all notes.

Configure the default user quota

Turn on the file types that you wish your users to be able to show on their portfolio pages.

Default user quota

**Institution**: Select the institution of the user.

When you create a token for a user, you need to provide some additional information.

**Institution**: Lists the institution in which the user is a member.

**Token**: The token that was generated for a particular user.

You can generate access tokens for individual users and associate service groups to which that user shall have access.

**Component**: The area through which a service group is available. It is generally "webservice".

Remove users from an institution

Uninvite users from joining your institution

Give users institution staff rights.

Give users institution admin rights.

Invite or add users to become institution members

Invite or add users to become institution members when they had left an institution

Configure the LDAP user sync

Faculty and students log in and are automatically placed into the institution "University". They see the standard university theme.

All these then still log in to the same Mahara institution. Alternatively, you could also separate the users into their own institutions on your Mahara installation if that is more appropriate for your use case. This could mean for the above example:

Alumni are placed into the institution "Alumni" for easier user management as you could have the alumni coordinator manage the users. Having them in a separate institution on Mahara would make it easy to see who an alumni is. Additionally, they could receive a slightly different university theme that is geared towards alumni, and they can also receive different messages on their dashboard.

**Page skins**: Switch this option on if you want your users who are not in a particular institution to use :ref:`page skins <skins>`.

Edit the "No institution" site institution

:index:`When the maximum number of accounts has been reached <single: Notification to administrators about full institution membership quota>` and another user tries to register for the institution, the site administrator as well as the institution administrator for that institution receive a notification. That allows them to take further steps.

**wstoken**: Enter the web services token for the user that you want to test.

**Authentication type**: Show the authentication type that is associated with the user.

**OAuth**: Select this option if you only want to see logs when the user logs in via OAuth.

**Institution**: Display the name of the institution in which the user is a member.

**User**: Display the logs when the user uses the username for the web service.

**Token**: Only display logs when the user has a user token.

**Protocol**: Show the protocol that is associated with the user for the chosen context.

**Appliation URI**: URI of the application.

**Service owner**: User who has set up the OAuth service.

**Server key**: The consumer key for the OAuth service.

**Service**: Select the service group that you want to set up for OAuth.