User Management Guide

User Management in Requestador is used to manage access to an organization and control what individual users are allowed to do within the platform.

It allows authorized users to:

• view current users in the organization

• invite new users

• assign roles

• change user roles

• disable user access

User Management helps ensure that access to Requestador is aligned with each user’s responsibilities and that only authorized users can modify platform configuration.

The purpose of User Management is to provide controlled access to Requestador based on user roles.

This is especially important when multiple users work in the same Requestador organization and not everyone should have the same permissions.

Typical goals include:

• limiting configuration changes to administrators

• allowing read-only or restricted access for non-admin users

• keeping ownership and administrative control within the organization

• managing who can create, edit, and maintain Requestador resources

Requestador currently supports the following roles:

Owner

The Owner is the primary account for the organization.

This role typically has full access to the organization, including administrative actions and overall account ownership.

Admin

An Admin can manage the Requestador workspace and perform configuration changes.

Admins can:

• invite new users

• manage users

• create, edit, and delete platform resources

• manage Requestador configuration across the platform

In practical terms, Admins have full CRUD access across Requestador.

Member

A Member has restricted access.

Members can:

• view and preview actions

Members cannot perform administrative or configuration-changing operations.

This role is intended for users who need visibility into Requestador actions but should not be allowed to create, edit, delete, or administer platform resources.

To open User Management, navigate to the User Management section in the main Requestador navigation.

The User Management page shows the current users in the organization and displays information such as:

• Email – the user’s email address

• Full Name – the name assigned to the user

• Role – the assigned Requestador role

• Status – whether the user is active or disabled

• Actions – available user management actions

This page is available only to users with sufficient administrative permissions.

Step 1: Open the User Management page

Navigate to User Management in the main menu.

Step 2: Click Invite User

Click the Invite User button.

This opens the invitation form.

Step 3: Enter user details

Complete the following fields:

• Email: Enter the email address of the user you want to invite.

• Full Name: Optionally enter the user’s full name.

• Role: Select the role that should be assigned to the new user.

  • Available role options include:

    • Member

    • Admin

Step 4: Send the invitation

Submit the invitation.

The invited user is then added to the organization according to the platform’s invitation workflow.

Administrators can change a user’s role from the User Management page.

Typical use cases include:

• promoting a Member to Admin

• reducing permissions for an existing user

• adjusting access as team responsibilities change

When changing roles, make sure the assigned permission level matches the user’s actual operational needs.

Use Admin only for users who should be allowed to manage and modify Requestador resources.

User Management also allows administrators to disable a user.

Disabling a user is useful when:

• a user should no longer have access

• a team member has changed roles

• access should be suspended without removing organizational history

A disabled user is no longer able to actively use the platform according to their previous role.

Use Member when:

• the user only needs visibility into actions

• the user should not modify configuration

• the user needs restricted access

Use Admin when:

• the user needs to manage Requestador resources

• the user should be able to invite other users

• the user is responsible for maintaining actions, catalogs, endpoints, and general platform setup

Use Owner when:

• the user is the primary organizational account holder

• full administrative and organizational control is required

• assign the lowest permission level that still enables the user to do their work

• use Member for users who only need to preview actions

• use Admin only for trusted users who need full configuration access

• review user access regularly

• disable users who no longer need platform access

• keep organization ownership under controlled and accountable users

Assigning Admin too broadly

Not every user needs administrative access. Overusing Admin increases the risk of accidental changes.

Using Member for users who need configuration access

Members can only preview actions and cannot manage resources. If a user needs to create or edit configuration, they must be assigned Admin.

Forgetting to disable inactive users

If a user no longer needs access, their account should be reviewed and disabled where appropriate.

Not aligning roles with responsibilities

Roles should reflect actual operational ownership and not only convenience.

User Management in Requestador controls who can access the platform and what they are allowed to do.

The main roles are:

• Owner – organization-level ownership and full control

• Admin – full administrative and configuration access

• Member – restricted access with action preview only

Use User Management to keep Requestador secure, organized, and aligned with team responsibilities.