Search docs.molo17.com

    Users and access settings reference

    Settings → Users & access is where you decide who can sign in to the Gluesync Control Plane and what they can do. This page describes every field and action of its three tabs, Users, User groups, and OIDC configuration, in the order the screen shows them. Each one has its own section.

    Available from Gluesync 2.3.3.0: a ? icon next to each setting in the Control Plane opens the section of this page that describes it.

    For a step-by-step walkthrough, follow the how-to guide Manage users, groups, and roles. To connect an identity provider from start to finish, follow Configure SSO with OIDC and map roles.

    Who can open Users & access

    The section is listed in Settings for the Manager and Super Admin roles only. The tabs inside it also depend on the role:

    Role Tabs shown

    Manager

    Users and OIDC configuration

    Super Admin

    Users, User groups, and OIDC configuration

    Viewers and Monitors do not see Users & access at all, and Core Hub refuses their requests to the user API with 403.

    Roles

    Every account has exactly one role. The role applies to the whole Gluesync instance, not to a single pipeline.

    Role In short

    Viewer

    Sees pipelines, entities, metrics, and notifications, and runs read-only queries in Query Studio. Cannot change anything.

    Monitor

    Everything a Viewer can do, plus start, pause, and stop entities, edit the settings of an existing entity, and save queries. Cannot create or delete pipelines, entities, or connections.

    Manager

    Builds and runs pipelines, manages connections and agents, changes global settings, and manages Viewer and Manager accounts.

    Super Admin

    Everything a Manager can do, plus managing accounts of every role, user groups, Query data access, and the OIDC configuration.

    The Users tab assigns only Viewer and Manager. A Monitor or a Super Admin account is created with the REST API, as shown in Create a Monitor or a Super Admin with the REST API. The full comparison of what each role can do is in Compare the roles.

    Users tab

    The Users tab creates local accounts, lists every account, and sets how long a sign-in lasts.

    Add account

    The Add account form creates a local account, that is an account that signs in with a username and a password stored in Gluesync. You do not choose the password: Gluesync generates a temporary one and shows it once the account exists. Create user stays disabled until Username is filled in and every field is valid.

    Username

    The name the person types to sign in. It is required, and it must be unique: Core Hub refuses a username that already exists.

    A username cannot start with an underscore (_). Those names are reserved for Core Hub’s own services, and Core Hub answers Usernames starting with '_' are reserved for Core Hub's own services.

    User role

    The role of the new account: Viewer (the default) or Manager. See Roles for what each role can do.

    A Manager can create only Viewer and Manager accounts. Core Hub refuses any other role from a Manager with Manager can only create users with role MANAGER or VIEWER.

    Name and Surname

    Optional. The person’s first name and last name. They appear under the username in the Accounts list. When this person later sends someone their credentials with Send via email, the email names them as the sender.

    Email

    Optional. The person’s email address. The form checks that it is a valid address.

    The address shows in the Accounts list. It is also where Send via email delivers the temporary password: without an address, that action is not offered.

    Temporary password

    After Create user, Gluesync shows Account created successfully and the Temporary password of the new account. The same message, titled Password reset successfully, follows a password reset.

    The password is shown only on this screen and only until you close the message: Gluesync stores only its hash. Hand it over in one of these ways:

    Copy password

    copies the password to the clipboard.

    Download CSV

    saves a file named <username>_credentials.csv with the columns username, password, role, name, surname, and email.

    Send via email

    sends the username and the password to the email address of the new account. The icon is offered only for a new account (not after a reset), only when the account has an email address, and only when email delivery is turned on with an SMTP server and a sender address in Settings → Notifications. When your own account has an email address, you are copied on the message. Gluesync confirms with Credentials sent by email.

    The account is created with Password change required: at the first sign-in, the person must choose a new password before anything else. The sign-in page asks for at least 8 characters, with 1 lowercase letter, 1 uppercase letter, 1 symbol, and 1 number.

    If the message was closed before the password was handed over, reset the password to get a new one.

    Accounts

    The Accounts list shows every account of the instance, split in two:

    Local

    accounts created in Gluesync, with the Add account form or the REST API.

    OIDC

    accounts created by a sign-in through the identity provider set in the OIDC configuration tab. Their role comes from the provider, through Role mappings and Default role for new users.

    Each tab shows its number of accounts. The search box filters the selected tab by username.

    Each row shows the username, the name, surname, and email address when they are set, and these labels:

    You

    the account you are signed in with.

    OIDC

    an account created by an OIDC sign-in.

    Password change required

    the person has not yet replaced the temporary password.

    The controls on the right of a row depend on the account and on your own role, as described in the next sections. Where a control is missing, the account cannot be changed that way from this screen.

    Change the role of an account

    Open the role list on the row and select Viewer or Manager. The change is saved at once.

    When the role changes, Core Hub ends every open session of that account: the person signs in again and works with the new role from then on.

    The role is shown as a read-only label instead of a list:

    • for the admin account;

    • for every Super Admin account;

    • for OIDC accounts, whose role comes from the identity provider;

    • for a Manager signed in, on Monitor and Super Admin accounts. A Manager can change only Viewer and Manager accounts.

    You cannot change your own role. Core Hub refuses it with Cannot change your own role, so that nobody locks themselves out of user management by mistake.

    Reset password

    The reset icon gives the account a new generated password, shown as a Temporary password, and sets Password change required again. Confirm with Reset.

    The reset icon is offered for local accounts only, and never for your own account, for the admin account, or for a Super Admin account. A Super Admin signed in can reset Viewer, Monitor, and Manager accounts; a Manager signed in can reset Viewer accounts. To change your own password, use Settings → Account.

    Delete user

    The delete icon removes the account after you confirm it. This cannot be undone. Along with the account, Core Hub:

    • removes it from every user group;

    • ends all of its sessions;

    • deletes the Query data access rules set on that user;

    • forgets the Enterprise brain memories it owns, when the Enterprise brain is in use.

    The delete icon is not offered for your own account, the admin account, or OIDC accounts. A Manager can delete Viewer and Manager accounts only; a Super Admin can delete any other account.

    Session duration (hours)

    How long a sign-in lasts, in whole hours. The default is 72, and the smallest value is 1. Select Save to apply it.

    The token issued at sign-in expires once this time has passed, so a session never lasts longer than this value, however active it is. A session that stays unused for this long also ends. The new value applies to the next sign-ins; tokens already issued keep the expiry they were given.

    The setting is for every account of the instance, local and OIDC alike, and Core Hub accepts the change from a Manager or a Super Admin. Over the REST API, it is PUT /session with {"sessionDurationHours": <hours>}.

    User groups tab

    A user group is a named set of users. It exists to give several users the same Query data access rules at once: a member’s access combines their own rules with the rules of every group they belong to. A group does not change what a role can do anywhere else in the Control Plane. To set the rules of a group, see Manage users, groups, and roles.

    Only a Super Admin can see this tab, and Core Hub accepts user group requests from a Super Admin only.

    New user group

    The form creates a group. Create user group stays disabled until Name is filled in and every field is valid.

    Name

    Required. The name of the group, at most 200 characters. It must be unique without regard to uppercase and lowercase: Finance and finance cannot both exist. The form says A user group with this name already exists before you save.

    Members

    Optional. The users in the group, local and OIDC accounts alike. You can create an empty group and add its members later with Manage members.

    Description

    Optional. A free text that says what the group is for. It shows under the group’s name in Current user groups and is searched by the search box. Leaving it empty clears it.

    Current user groups

    The list of the groups, sorted by name. Each row shows the name, the number of members, and the description. The search box filters by name and description.

    Edit user group

    The edit icon renames the group or changes its description. The same rules as in New user group apply to the name.

    Manage members

    The members icon opens Members of <group>, where you add or remove users. Save members replaces the whole member list with the one you selected.

    Delete user group

    The delete icon removes the group after you confirm it. This cannot be undone. The Query data access rules set on the group are deleted with it, so its members lose any access they had only through this group. The user accounts themselves are not touched.

    OIDC configuration tab

    OpenID Connect (OIDC) lets people sign in to the Control Plane with an external identity provider, such as Keycloak, Microsoft Entra ID, Okta, Auth0, or Google, instead of a Gluesync password. The sign-in uses the authorization code flow with PKCE.

    The tab is shown to Managers and Super Admins, but only a Super Admin can save it. Core Hub refuses a save from any other role with You don’t have permission to update OIDC configuration.

    For the provider side of the setup, see OIDC authentication and the provider pages for Keycloak, Microsoft Entra ID, and Auth0.

    Enable OIDC authentication

    Turns sign-in through the identity provider on or off. The settings below appear only while it is on.

    Turning it on fills in Redirect URI when that field is empty. Nothing is saved until you select Save OIDC configuration.

    Turning it off saves at once, without Save OIDC configuration, and clears the stored provider settings: provider name, issuer URL, client ID, client secret, redirect URI, scopes, role claim path, role mappings, and denied groups. Turning OIDC on again means entering them again.

    Accounts created by earlier OIDC sign-ins stay in the OIDC list of Accounts.

    Provider name

    Required while OIDC is on. A name for the identity provider, for example Keycloak or Azure AD. The sign-in page shows it on the provider button, as Login with Keycloak. It does not affect the sign-in itself.

    Issuer URL

    Required while OIDC is on, and it must start with http:// or https://. The base URL of the identity provider, for example https://keycloak.example.com/realms/gluesync.

    Core Hub reads the provider’s discovery document from <issuer URL>/.well-known/openid-configuration and takes the authorization, token, user information, and sign-out endpoints from it. A trailing slash on the URL does not matter.

    Client ID

    Required while OIDC is on. The identifier of the client application that you registered for Gluesync in the identity provider.

    Client secret

    The secret of that client application. It is required the first time you save an enabled configuration.

    Once saved, the secret is never shown again: Core Hub returns it empty when the configuration is read. The field then says Leave blank to keep existing secret: leave it empty to keep the stored secret, or enter a new value to replace it.

    Redirect URI

    Required while OIDC is on. The address the identity provider sends the browser back to after the sign-in. Gluesync fills it in with <Control Plane address>/oidc/callback, built from the address you opened the Control Plane with.

    Register exactly this URL as an allowed redirect URI of the client application in the identity provider. Change it only if people reach Gluesync through another address, for example a load balancer, and register that one instead.

    Scopes

    The scopes Gluesync requests from the identity provider, separated by commas. The default is openid, profile, email. Add the scope your provider needs to put roles or groups in the token or in the user information, when it has one.

    Role claim path

    Where Gluesync finds the person’s roles or groups in what the identity provider returns. The default is roles.

    • A name such as roles or groups reads that claim.

    • Dots go down into nested claims: realm_access.roles reads the realm roles of Keycloak. Write \. for a dot that is part of a name.

    • A claim whose full name matches the path is read first, so a namespaced claim such as https://gluesync.com/roles works as it is.

    The claim can hold a list or a single value. Gluesync looks in the user information first, then in the ID token, then in the access token. If the path finds nothing, the person gets the Default role for new users. More examples are in How Core Hub resolves the role claim.

    Token refresh interval (minutes)

    How often, in minutes, Core Hub checks every open OIDC session with the identity provider. The default is 60; a value below 1 counts as 1.

    At each check, Core Hub uses the refresh token of the session:

    • when the provider no longer accepts it, for example because the person was disabled or signed out there, the Gluesync session ends;

    • when the person now belongs to a denied group, all of their sessions end;

    • when the role resolved from the provider has changed, the account takes the new role and all of its sessions end, so the next sign-in carries the new role.

    Sessions for which the provider issued no refresh token are not checked. They last until Session duration (hours) ends them.

    Skip TLS verification

    Off by default. When on, Core Hub accepts any TLS certificate from the identity provider, including self-signed and expired ones, for every call it makes to it. Use it only for a test provider with a self-signed certificate, never in production.

    Default role for new users

    The role given to a person whose roles or groups match none of the Role mappings: Viewer (the default) or Manager.

    Despite the name, it is applied at every sign-in, not only to new accounts: the role of an OIDC account is worked out again from the provider each time.

    Role mappings

    Each mapping links a role or group name from the identity provider, OIDC role/group, to a Gluesync role, Gluesync role (Viewer or Manager). Select Add mapping to add one and the delete icon to remove one.

    At each sign-in, Gluesync reads the person’s roles or groups at the Role claim path and goes through the mappings from top to bottom. The first mapping whose name matches one of them, without regard to uppercase and lowercase, decides the role. When none matches, the person gets the Default role for new users.

    On the first sign-in, Gluesync creates the account with that role and lists it in the OIDC tab of Accounts. On later sign-ins, it updates the role when it has changed. Because the role always comes from the provider, an OIDC account has no role list in Accounts.

    Prevent user access: Denied groups

    OIDC roles or groups whose members cannot sign in, separated by commas. Names are compared without regard to uppercase and lowercase.

    • A person who has any of the listed roles or groups is refused with Access denied: your group membership is not allowed to access this portal.

    • * turns on allowlist mode: a person is refused unless at least one of their roles or groups appears in the Role mappings.

    The rule is checked at every sign-in and at every token refresh, so adding someone to a denied group in the provider also ends their open Gluesync sessions.

    Save OIDC configuration

    Saves the configuration. It is enabled once the form is valid. Core Hub checks again that the issuer URL, client ID, client secret, and redirect URI are present before it saves an enabled configuration. Gluesync confirms with OIDC configuration saved successfully.

    Once saved and enabled, the sign-in page of the Control Plane offers sign-in through the provider, next to the username and password form.

    Test connection

    Checks the saved configuration: save your changes first. The button is available only when an enabled configuration with an issuer URL, a client ID, and a redirect URI is saved.

    The test reads the provider’s discovery document from the issuer URL and builds the authorization URL from it. OIDC connection test successful! Authorization URL generated. means that Core Hub reached the provider and found its endpoints. It does not sign anyone in, so it does not check the client secret, the redirect URI registration, or the role mappings: sign in through the provider in a private window to check those.