Skip to main content
ServiceAuthentication
Availability8.6.0 or later
User Access Requests GermainUX allows prospective users to request access to the Germain Workspace. Administrators can review each request, assign the appropriate Roles and Teams, and then approve or reject it.

Request Access

Submit a login access request

Approve an Access Request

Review, approve and assign roles

Review Request History

Audit past access requests

Recommended Practices

Guidance for access approvals

​
This workflow helps organizations:

​
Request Access

From the GermainUX login page:
  1. Click Request Access.
    User Access Request: Request Access
  2. Enter the required user information.
  3. Submit the request.
    User Access Request: Request Access, image 2
  4. Wait for an administrator to review it.
Submitting a request does not immediately grant access. The requester can sign in only after an administrator approves the request and the account setup is completed.

​
Review Access Requests

Administrators can review pending requests from the Germain Workspace. Go to: Germain Workspace -> Left Menu -> Settings —>System -> Auth Settings -> Access Requests
User Access Request: Review Access Requests
Select a request to review:
  • Requester’s identity and email address
  • Date and time of the request
  • Requested access
  • Current request status
  • Any additional information provided by the requester
Before approving the request, verify the requester’s identity and confirm that access is required for their responsibilities.

​
Approve an Access Request

To approve a request:
1

Go to System -> Auth Settings -> Access Requests

2

Select the pending request

3

Review the requester’s information

4

Assign the appropriate Roles

5

Assign the user to the appropriate Teams

6

Click Approve

After approval, GermainUX creates or enables the user account and notifies the requester when applicable. Assign only the Roles and Teams required for the user’s responsibilities.

​
Reject an Access Request

To reject a request:
1

Go to System -> Auth Settings -> Access Requests

2

Select the pending request

3

Review the requester’s information

4

Click Reject

5

Enter a reason when required

6

Confirm the rejection

Reject requests when:
  • The requester’s identity cannot be verified
  • Access is not authorized
  • The request is incomplete
  • The requested permissions exceed the user’s responsibilities
  • The request was submitted accidentally or more than once
Rejecting a request does not create or enable a GermainUX account.

​
Review Request History

The access-request list provides a record of submitted requests and their status. Depending on the available filters, administrators can review:
  • Pending requests
  • Approved requests
  • Rejected requests
  • Requesters
  • Reviewers
  • Submission and decision dates
This history helps administrators investigate previous decisions and support access-control reviews.

​
Manage an Approved User

After approving a request, manage the account from: Germain Workspace -> Left Menu -> Settings-> System -> Auth Settings -> Users From the Users page, an administrator can:
  • Update assigned Roles
  • Update Team memberships
  • Reset the user’s password
  • Enable or disable the account
  • Remove access when it is no longer required
  • Verify each requester before granting access.
  • Apply the principle of least privilege.
  • Assign Teams according to data-visibility requirements.
  • Avoid granting administrative Roles unless necessary.
  • Document the reason for rejected requests.
  • Periodically review approved users, Roles, and Team memberships.
  • Disable or remove accounts that no longer require access.

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.