Create a ChannelRUSH login, assign the right actions and properties, and manage password resets, account lockout and user deletion.

## Before you start

You need **Org Admin** access to manage users. The **Property Admin** role does not include user management. For your own contact details, preferences, password or two-factor authentication, use [My Profile](https://help.channelrush.com/hc/channelrush/articles/my-profile).

Select a property in the organization you want to manage. Open **Org Admin → Org Edit → Users**. Expand **Users** if the table is collapsed. Check the organization name and ID before adding or editing anyone.

Keep another active Org Admin available before reducing your own administrative access or disabling an administrator. Property access and action permissions are separate: being able to open a property does not authorize every change there.

## Add or edit a user

1. In **Users**, select **Add New**, or **Edit** beside the intended user.
2. For a new user, enter **Login Email**. Use a valid address that is unique within this organization and meets any approved-domain policy. An existing user's login email is read-only here; contact Support if it needs changing.
3. Enter the person's name and contact details. Select **Time Zone** and **Language**. A time zone is required when saving a new or changed user.
4. Under **Permissions**, choose a **Role**, or choose **Custom** and review the individual boxes below.
5. Under **Property Access**, choose the properties the user should access. Review the current-and-future switch separately from the current-property checklist.
6. In **Settings**, choose an accessible **Initial Property**, then review the start page, dashboard and email preferences. The field reference below explains each choice.
7. Leave **Reset Password** at **No** and the password fields empty unless this is an intentional security change. Arrange two-factor setup with the account owner rather than collecting their password or codes.
8. Select **Save** to save and leave the editor. To save and stay, open the arrow beside **Save** and choose **Save & Refresh**.

**Cancel** leaves without submitting the current edits. It does not undo an earlier save. Role, permission and property selections are pending until you save.

A new user normally starts with the **Reservations** role, **Active** status, current properties in the user's own organization selected, and **All properties, current and future** off. Child-organization properties are not automatically selected. If the organization has no active users, the new user instead starts as **Org Admin**, with the current-and-future switch on. Always review the defaults before saving.

For a new portal user, saving creates a temporary password and requests an account-instructions email to **Login Email**, even though **Reset Password** initially displays **No**. The user must change the temporary password when signing in. Account creation and a reset notice do not prove that the email reached the inbox.

**Check the result:** return to **Users**. Confirm **Role**, **Properties** (**All** or a selected count), **Announcements** and **Active**. Reopen **Edit** to check the exact permissions, property selections and Initial Property. A later password or two-factor error does not mean the earlier profile and access changes were rolled back.

## Choose a role

Roles control actions at accessible properties. Most operational information remains viewable without its editing permission; card details and channel login information have separate protections.

| Role | What it allows |
| --- | --- |
| **Org Admin** | All customer permissions, organization settings and user management, with access to every property in the organization. |
| **Property Admin** | Property settings plus channel, booking engine/CRS and content settings, inventory updates, reservation actions and guest communication. No user management. |
| **Manager** | Channel, booking engine/CRS and content settings, inventory updates, reservation actions and guest communication. No property settings or user management. |
| **Revenue** | Rates, availability, restrictions, promotions and pricing rules, plus reservation actions, card details, guest messaging and review drafts. No general settings access. |
| **Reservations** | Reservation actions, card details, guest messaging and review drafts. No inventory updates or settings changes. |
| **View only** | View accessible properties without changing operational data. No protected card details or channel login information. Own-profile editing remains available. |
| **Custom** | Use the individual permission boxes instead of a preset role. |

Guest messaging and reviews also depend on feature availability. **Manager**, **Property Admin** and **Org Admin** can publish review replies. **Reservations** and **Revenue** can manage drafts but cannot publish replies.

A preset role selects and locks the boxes it controls. Switching to **Custom** unlocks those boxes without clearing them: it starts from the permissions currently selected. Switching back to a named role replaces the role-controlled selection. The separate standard-only restriction is not cleared by choosing another role.

## Set Custom permissions

1. Set **Role** to **Custom**.
2. Select or clear the individual permissions needed for the user's work. Do not grant a whole group merely to enable one task.
3. Review **Org Admin** and **Update - Standard Room Types & Rate Plans Only** separately; neither is part of a group select-all.
4. Review **Property Access**, then save and reopen the user to confirm the final selections.

The **System**, **Channel Manager**, **Guest Messaging** and **Booking Engine / CRS** heading checkboxes select or clear the enabled boxes within that group. A dash means some are selected. The adjacent count summarizes that group, not the user's complete access.

![Custom role and organization, property-settings, channel-manager permissions and standard-only restriction](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcGtCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--0a4a27ce568b7e1dc0b77c57035421dc83cefa7c/users-permissions.png)

| Permission box | What it changes |
| --- | --- |
| **Org Admin** | Organization administration, user management and access to all properties in the organization. In Custom, this box does not replace the other action-permission boxes; the named Org Admin role selects the full preset. Do not use individual property boxes to restrict someone who has Org Admin. |
| **Property Settings** | Change property-level settings, such as time zone, office hours, default restrictions, reservation email settings and property AI settings. It does not grant user management. |
| **Update - Availability** | Change allocation and Stop Sell, including opening or closing availability. Stop Sell belongs to Availability, not the Restrictions permission. |
| **Update - Rates** | Change rates and extra rate values. Also allows pricing-rule work such as promotions, rate calculations, occupancy pricing, rounding and date-range markups. |
| **Update - Restrictions** | Change booking restrictions such as minimum/maximum nights, through-stay limits, closed to arrival/departure and cutoff days, plus supported channel-specific update parameters. |
| **Reservations - Actions** | Perform supported reservation operations, including channel actions and sending reservations. It also permits saved-report management. It does not reveal protected card details by itself. |
| **Reservations - Credit Card** | View protected reservation card details, subject to the page's password re-verification and other card-display requirements. |
| **Channel Settings** | Change channel setup and mappings. Also permits channel pricing rules and saved-report management. |
| **Channel Settings - Login Info** | Access protected channel login information. Combine it with Channel Settings to edit those protected setup fields, or with Booking Engine / CRS Settings for booking-widget key management. |
| **Guest messaging - Send and manage** | Send and manage guest conversations where the feature and channel support them. Reading available messages does not require this editing permission. |
| **Guest reviews - Manage drafts and attention** | Work on reply drafts and review attention status without publishing a public reply. |
| **Guest reviews - Publish publicly (requires Manage)** | Publish public review replies. Saving this permission also requires and grants Manage. To remove both, clear both boxes; leaving Publish selected restores Manage on save. |
| **Booking Engine / CRS → Settings** | Change booking engine/CRS setup and related settings. Also permits its promotion management. |
| **Booking Engine / CRS → Content** | Edit property content, such as descriptions and media. |

![Guest messaging, review-draft and public-publishing permissions, followed by booking engine and CRS settings and content permissions](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcG9CIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--75ad7e719ccebdbccfa44642ae865b8403ac9beb/users-guest-permissions.png)

Guest messaging and review boxes appear only when those features are available. Reading available reviews does not require a separate View box. A missing feature cannot be enabled by selecting an unrelated permission. Channel-specific capabilities and property setup still apply after a permission is granted.

### Understand the standard-only restriction

**Update - Standard Room Types & Rate Plans Only** is a restriction, not permission to update inventory. The user still needs the applicable Rates, Availability or Restrictions permission.

When selected, it applies standard-only mode to **Quick** and **Detail**:

- **Quick:** the channel-selection checklist is hidden. Updates use eligible configured channels rather than a manually selected subset.
- **Detail:** channel-specific room/rate inputs are disabled and channel-specific controls are limited. Use the standard-property room types and rate plans for the update.
- Standard-product updates can still generate updates for mapped channel products. This is not a setting to stop channel delivery or to confine an update to one channel.

Leave it clear when the user should not have this additional restriction. Clearing it does not override the property's own **Standard Room Types & Rate Plans Only** update mode. These user-checkbox effects are established for Quick and Detail. Do not rely on this checkbox alone as an across-all-screens security policy. Ask Support to confirm the setup if a strict standard-only policy is required.

## Choose current, future and child-organization properties

### Selected current properties

1. For a user without Org Admin access, turn **All properties, current and future** off.
2. Under **All Properties**, select the individual current properties they need. Clear any they must not access.
3. Use the **All Properties** heading checkbox only when you want to select or clear the current list. It does not grant future properties.
4. Choose an accessible **Initial Property** in **Settings**.
5. Save, reopen the user and check the selections.

Turning the current-and-future switch off unlocks the existing selections; it does not clear them. Clear unwanted properties explicitly. Leaving all applicable property lists empty does not mean “all”; it leaves a non-Org-Admin user without property access and can prevent sign-in.

![Property Access with the separate current-and-future switch and current-property checklist](https://support.channelrush.com/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBcHNCIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--fcb806780fd3d0c578c67e2457b046c29a3d9bc1/users-property-access.png)

The illustration shows no properties selected. For a user without Org Admin, select the required properties rather than saving that empty selection.

### All current and future properties

Turn **All properties, current and future** on when the user should receive access to every active property in their own organization, including properties added or reactivated later. The current-property boxes become selected and locked. Save to apply the choice.

This switch does not automatically include every child-organization property. It also remains independent of the role: reducing an Org Admin's role while leaving this switch on still gives that user all current and future properties in their own organization.

**Org Admin overrides property restrictions.** A user with the Org Admin role or Custom Org Admin box can access all properties in the organization even with the switch off or boxes cleared. Remove Org Admin first if access must be limited, then review the switch and individual properties before saving.

### Child-organization property lists

Some organization structures display additional groups headed **Org [ID] - [name]** below the main checklist. These groups are conditional; a normal organization may have none, and they are not shown for a target user who already has Org Admin access.

1. Open the non-Org-Admin user's editor from the organization that owns the user.
2. Scroll below the main **All Properties** list to the intended child organization's heading.
3. Select individual properties, or use that organization's heading checkbox to select or clear its current list.
4. Repeat for each child organization required. The main current-and-future switch and the main All Properties checkbox do not select these groups.
5. Save, reopen the user and check each child group separately.

A child group's heading checkbox affects only its displayed properties. It is not a future-property grant. Revisit access when a child organization adds properties. If the required child group or property is missing, ask Support to check the organization relationship and active-property setup; do not change unrelated access to work around it.

**Initial Property is a preference, not an access grant.** Its dropdown lists properties from the user's own organization, while separately assigned child properties may not appear there. Do not infer access from a displayed default: check Property Access. On save or entry to the application, an unavailable default can fall back to an assigned property. For a child-only user, confirm the resulting accessible property after saving rather than promising a specific dropdown choice.

## Reset a password

Use this for another user's account recovery, not for an ordinary profile edit.

1. Open the intended user's **Edit** page and confirm **Login Email**.
2. Under **Login Info**, set **Reset Password** to **Yes**.
3. Select **Save**, or **Save & Refresh** to remain on the editor.
4. Read the result and ask the user to check for **ChannelRUSH - User Account**, including junk mail. They must use the temporary password and choose a new password at sign-in.

The reset replaces the previous password. Repeating it replaces the earlier temporary password again; do not keep resetting because an email is delayed. A notice that an email was sent is not proof of receipt. Contact Support if delivery or the result is unclear.

Leave **Change Password** fields blank when managing another person's account. Do not ask for their current password, use your own password in their form, or request a verification code. For your own password change, follow [My Profile](https://help.channelrush.com/hc/channelrush/articles/my-profile).

## Disable, reactivate or delete a user

### Disable access without deleting the record

1. Open **Edit** beside another user.
2. Set **User Account Status** to **Disabled - Locked Out**.
3. Save, then check **Active = No** in **Users**.

Lockout prevents sign-in. An existing signed-in session ends when the application next checks the user. You cannot change your own account status in this form. Keep an active Org Admin available.

To reactivate, change the status to **Active**, save and confirm **Active = Yes**. Recheck the role and property assignments. Connected-AI authorizations revoked by lockout are not restored automatically; the user must reconnect them separately.

### Delete an eligible user

Prefer disabling a former staff member when you need to preserve the account record or deletion is refused. Deletion removes the user rather than temporarily locking them out; there is no undo control on this page. It also removes that user's saved-report recipient assignments and revokes connected-AI authorizations. Confirm who should receive any required reports before deleting.

1. Return to **Org Admin → Org Edit → Users**.
2. Select **Delete** beside the intended user. This opens **Delete User**; opening it alone does not delete the account.
3. Check the login email and the message **Are you sure you want to proceed with this delete?** Select **Cancel** to return without deleting.
4. Only when certain, select the red **Delete** button on that confirmation page.
5. Check the success message and confirm the user no longer appears in **Users**.

Deletion eligibility is checked when you confirm, not merely when the Delete link is shown. A user who has never logged in is eligible. For a user who has logged in, the system checks recorded user activity: recent activity within the preceding 180 days prevents ordinary deletion. Last Login alone is not the deletion test.

If the page says **Unable to delete this user. The user has transactions that exist in the system, disable / lock out the user instead**, return to the user's editor and disable the account. Do not repeatedly try deletion or assume that the confirmation page established eligibility. If a deletion result is uncertain, refresh the Users list before taking another action and contact Support if the record's state remains unclear.

## Field reference

### General Settings and preferences

| Field | Values, defaults and use |
| --- | --- |
| **Login Email** | Required for a new user; valid email, unique within the organization and subject to its approved-domain policy. Read-only for an existing user. Account/reset emails use this address. |
| **User Account Status** | **Active** or **Disabled - Locked Out**; new users start Active. Not offered when editing your own account. |
| **Last Login Timestamp** | Read-only last sign-in time, or **Never logged in.** It does not establish deletion eligibility on its own. |
| **Edit Timestamp** | Read-only saved-edit time. Both timestamps display in the signed-in editor's time zone. |
| **First Name**, **Last Name** | Contact names used to identify the user. These start blank; neither replaces Login Email. |
| **Job Title** | Optional job or responsibility, such as Revenue Manager. Starts blank. |
| **Mr / Mrs / Ms** | Optional free-text name prefix; starts blank. |
| **Phone**, **Alt Phone** | Optional contact numbers; start blank. They are separate from the two-factor phone number. |
| **Time Zone** | Choose from the searchable list. New-user setup derives a default from the organization; confirm it rather than assuming it matches the editor. A selection is required to save changes. |
| **Language** | **English**, **German** or **Spanish**. The new-user form initially displays English; review it for the user. |
| **Start Page** | Blank, **Updates - Quick**, **Updates - Detail**, **Updates - Daily**, **Updates - Status**, **Updates - Status Summary**, **Reservations**, or **Reservations - Arrivals**. Sets the entry destination when no specific return destination is supplied. New users start blank. |
| **Dashboard Report** | Choose a listed saved report, or leave blank for the standard dashboard. New users start blank. The list is based on reports available to the signed-in editor; confirm report sharing/access before selecting one for someone else. |
| **Initial Property** | Starting property when no specific property is selected. The new form can display the first listed property. Review it against Property Access; changing the preference does not immediately switch the property you have open. |
| **Update Summary** | **No**, **Yes**, or **Yes - On Unsuccessful Only**. Controls inventory-update processing emails, not reservation notifications. A normal new portal user defaults to unsuccessful-only. |
| **Update Summary Frequency** | **Once Daily** or **After Processing Complete**; normal new-user default is Once Daily. No summaries are requested through this preference while Update Summary is No. Delivery depends on update activity and processing, not an immediate-delivery promise. |
| **Important System Announcements** | **Yes** or **No**; normal new-user default is Yes. Some essential property notices can still be sent when no opted-in recipient is available. |

Update summaries concern the user's assigned properties, not only Initial Property. These preferences are separate from saved-report email schedules. A saved preference does not confirm email delivery.

### Login Info and conditional two-factor fields

| Field | Values, defaults and use |
| --- | --- |
| **Reset Password** | **No** or **Yes**; normally No. Yes replaces the password when saved and requests account email. New portal users receive initial account instructions on creation without manually selecting Yes. |
| **Re-Verify Password - Minutes** | Blank, **0**, or a whole number from **1 to 32,767** minutes, such as **15**. Blank disables this timed password re-check; 0 requests re-verification each time a protected page requires it, with a short allowance for the return redirect. Positive values reuse a recent password verification for that interval. This is not the login-session lifetime or two-factor interval. |
| **Enter Current Password**, **Enter New Password**, **Enter New Password Again** | Shown for existing users. Leave all three empty for an ordinary management edit. The account owner should use My Profile for a password change; a new password must match its confirmation, have at least eight characters, differ from the current and immediately previous password, and not contain or be contained in the login email. |
| **Two-Factor Authentication → Enabled** | **Yes** or **No**; normal new-user default is No. The section is available for a new user or your own account, but not normally when a customer Org Admin edits another existing user. Enabled alone is not completed enrollment. |
| **Type** | **SMS / Text**, **Authentication App**, **Voice Phone Call**, or **Email**. New-user default is SMS / Text. Read-only while enabled. Email uses Login Email. |
| **Days Before Re-Verify** | **0 - Verify Every Login**, **1 Day**, **7 Days**, **14 Days**, **30 Days**, **60 Days**, or **90 Days**; new-user default is 90 Days. Remembers two-factor verification in that browser for the selected period; another browser or cleared cookies can require it sooner. |
| **Activation Timestamp** | A date/time establishes completed activation. **-** means no completed activation is recorded. Displayed in the editor's time zone. |
| **Phone Number Country**, **Phone Number** | Separate two-factor destination, required for SMS or voice. Select a country whenever providing a number. These start blank and become read-only while enabled. |
| **Authentication App QR Code**, **Enter Verification Token To Activate** | Conditional enrollment controls after setup starts. Treat the QR and token as secrets. The account owner completes verification; never send either to Support or include them in a screenshot. |

For ordinary user onboarding, have the account owner complete the step-by-step [My Profile two-factor setup](https://help.channelrush.com/hc/channelrush/articles/my-profile). They must verify a code and check Activation Timestamp; saving Enabled = Yes is not sufficient. For accounts that require two-factor authentication during user creation, coordinate the setup with the owner and Support before saving; follow the displayed requirement rather than disabling the policy.

## Resolve common problems

- **Email already exists:** locate and edit the existing user in this organization instead of adding a duplicate. Ask Support if you cannot find the matching record.
- **Invalid or unapproved email:** correct the format or use an approved company domain. Contact Support to review the organization's allowed domains.
- **Time zone required:** select a real Time Zone rather than **Select ...**, then review the form before saving again.
- **Permissions are greyed out:** a named role locks its boxes. Choose Custom only if an individual permission set is intended. If user management itself is unavailable, ask an Org Admin.
- **Property access did not narrow:** check for the Org Admin role or box and the current-and-future switch. Turning the switch off does not clear previously selected properties. Check child groups separately.
- **User cannot sign in after access changes:** confirm Active status and at least one intended active property assignment. Check the organization used at sign-in. Contact Support if these are correct; do not repeatedly reset the password to fix a property-access problem.
- **Password or two-factor error after saving:** profile/access changes may already have saved. Reopen the user to inspect non-secret settings. A password change can also precede a later validation error; do not assume the old password still works or repeatedly submit the same change. Ask Support if the outcome is unclear.
- **Pending authenticator setup rejects a code:** the owner should use the app entry for the currently displayed QR. Saving pending setup again without a token can replace enrollment and invalidate an earlier scanned entry. Do not restart it repeatedly.
- **PMS Connect creation is blocked:** partner-managed property users sign in through the partner's application. ChannelRUSH creates a PMS Connect account's first administrator; its later staff additions can require two-factor authentication. Follow the displayed message or contact Support.

For Support, provide the organization, affected login email, action time/time zone and displayed error. Never include passwords, verification codes or enrollment QR codes.

## Related

- [My Profile: preferences, password and two-factor setup](https://help.channelrush.com/hc/channelrush/articles/my-profile)
- [Accounts](https://help.channelrush.com/hc/channelrush/articles/accounts-page)
