You tried to open a page or use a button, and the Console stopped you with an Access Denied message, a greyed-out button, or an application or Rhythm account that would not open. Use this page to match what you saw, understand the access you need, and know who can fix it. This guidance applies to every application's Console. For background, see How the Console Decides What You Can See.
Tip
If several unrelated pages or actions fail at the same time, or other people at your organization see the same issue, check Rhythm's public status page before you spend time on permissions or your browser. A broader service incident can look exactly like an access problem; see cause 8 below.
Match the Message
Start with what you see. Each refusal uses its own wording.
| What you see | What was refused | Go to |
|---|---|---|
| Access Denied: You must have permission name permission for the requested resource. | The Console blocked the page you tried to open and kept you on the page you were already using | Cause 1 |
| A button stays greyed out, and its hover text reads Access Denied: You must have permission name permission for the request resource in order to continue. Please see your system administrator. Or, when you click a button, you see Access Denied instead of its usual confirmation | A button or action | Cause 1 |
| A link cannot be clicked and shows the same hover text | A link | Cause 1 |
| You do not have sufficient privileges to login to the console at this time. | Opening the Console at all | Cause 1 |
| A sign-in message says you do not have sufficient privileges to sign in to this Rhythm account or sandbox. | Working in this Rhythm account or sandbox | Cause 2 |
| You do not have sufficient privileges to access this application., or Access Denied: You do not have adequate security privileges to access the application application | Opening this application | Cause 1 |
| Application Disabled says your Rhythm account or sandbox does not have access to this application, or you see Application Not Available | The application is not switched on for your Rhythm account or sandbox | Cause 5 |
| A switching message says you do not have sufficient security privileges to access the Rhythm account or sandbox you selected. | Switching to another Rhythm account or sandbox | Cause 2 |
| A refusal to run, download, or schedule a query | A query action | Cause 1, and Design and Run a Query |
| A button is greyed out for a moment, then becomes available | Nothing; the Console was checking | Cause 6 |
| The Console keeps showing Logging you in... just a moment..., or spins with no error message at all | The Console is likely stuck reaching an account or sandbox you cannot open, or there is a broader service problem | Cause 2, or cause 8 |
| Saving fails with a generic error such as Unknown Error, on more than one kind of record | The same refusal behind an Access Denied message may be appearing as a generic failure instead | Cause 8 |
| A page, search, or query loads endlessly, shows a blank screen, or behaves differently only in one browser, device, or network | Your browser, device, or network is likely the issue, not a permission | Cause 7 |
Every Access Denied message includes an OK button and a close icon. When you close the message, you stay where you were and keep anything you typed because the refused page or action never ran. If the message appears while the Console is opening, the Console stays empty behind it; use the top bar or the address bar to go somewhere else.
1. You Do Not Have the Permission
Why. Your organization's security settings decide which pages and actions each person can use. The message shows the permission you lack where permission name appears.
Check. Read the permission name exactly as shown. For a greyed-out button, point to it with your mouse to read the text. On a touch screen, or when you only use a keyboard, that text may not appear, so use a mouse if you can. Ask a colleague whether they can use the same page or button in the same Rhythm account or sandbox. If they can, your permissions are different. If you are checking by impersonating the other person from the Console, remember that the request still uses your access, not theirs. A successful action while impersonating does not prove the other person's access works, so ask them to try it themselves or describe exactly what they see.
Fix. Send your administrator the permission name, copied exactly, along with the page or button you were using and the account or sandbox name from the top bar. The message does not include a way to request access. Your administrator grants the permission in your organization's security settings.
A permission can be granted for your whole organization, for one Rhythm account or sandbox, or for one record. That means you may be allowed to use an action on one record and refused on the next, or allowed to open a page but refused a button on it. Tell your administrator which record you were on. Some actions need a permission separate from general administrative access. For example, administering task queues needs its own permission, so an administrator without it sees the same Access Denied message when trying to add one.
2. You Are in a Different Account or Sandbox
Why. Your organization sets access separately for each Rhythm account and sandbox. An action can work in your live account and be refused in your sandbox. It can also work in your sandbox and be refused in your live account.
Check. Look at the account or sandbox name in the top bar. A sandbox also shows Sandbox mode.
Fix. Switch to the account or sandbox you meant to use; see Switch to Another Account or Sandbox. If the refusal was for that account or sandbox, ask your administrator for access. If you land in the wrong account or sandbox each time you sign in, see Sign In and Choose Your Account.
An account or sandbox can also be turned off entirely, and nobody can open it until Rhythm turns it back on. If sign-in shows Logging you in... just a moment... for a few seconds, sends you back to sign in, and possibly repeats several times without explaining why, contact Rhythm Support or your administrator instead of continuing to retry.
3. The Permission Was Granted a Moment Ago
Why. The Console reuses each answer about your access for five minutes, so it does not have to check again on every page. If your administrator just granted a permission, it can take up to five minutes to reach a Console you already have open.
Check. Ask when the change was made.
Fix. Wait five minutes, then open the page again or reload it. If it is still refused after that, go back to cause 1 and confirm with your administrator that the permission was granted for the right Rhythm account or sandbox and, where it applies, the right record.
4. The Button Is Waiting for Something Else
Why. Many buttons are greyed out for reasons other than permissions. A Save Changes button stays unavailable while a form has errors. A form's Next stays unavailable until the page's questions are answered.
Check. Hover over the button. If no Access Denied text appears, the button is probably waiting for something on the page, not for a permission.
Fix. Look for a Form Errors card or messages under the fields, then correct them. For forms members and staff fill in, see Fill In a Portal Form.
A link or tab can also stay visible in the Console after the feature behind it has been retired. Clicking it produces a generic error such as Something went wrong, with links that do not respond, rather than an Access Denied message. This is not a permission problem; report it to Rhythm Support so the stale entry can be removed.
5. The Application Is Not Available in Your Rhythm Account or Sandbox
Why. Each Rhythm account and sandbox has its own set of Rhythm applications, based on what your organization has from Rhythm. Application Disabled and Application Not Available mean the application is not switched on for the account or sandbox you are using. A permission cannot turn it on.
Check. Open the application list in the top bar; see Move Between Applications and Recent Records. The list shows only applications you can open. If nobody in the same Rhythm account or sandbox can open the application, it is not switched on there.
Fix. If your organization should have the application, contact Rhythm Support and name the Rhythm account or sandbox and the application.
6. The Console Is Still Checking
Why. When a page opens, buttons that require a permission are greyed out briefly while the Console checks whether you may use them. They become available as soon as the answer is yes.
Fix. Wait a moment. If the button stays greyed out, hover over it and go to cause 1 or cause 4.
7. Your Browser, Device, or Network Is the Cause
Why. Not every refusal comes from your permissions. Local browser data, an unsupported or out-of-date browser, security or web-filtering software on your computer or network, or the network path itself can produce a blank page, an endless spinner, or even a misleading Access Denied message. This can happen when you open a page, run a search, initialize a form, load a record, or execute a query.
Check. Work through these checks to narrow it down:
- Open the same page in a private or incognito window. If it works there but not in your normal window, cached site data or a browser extension in your normal window is the likely cause.
- Try another, up-to-date browser. Rhythm is optimized for Chrome; Firefox is also a good option. If the page only fails in one browser, the cause may be an unsupported or misconfigured browser rather than Rhythm.
- Try another device, including a phone if that is where you saw the problem. On a phone, confirm it has the latest operating system update, then clear the mobile browser's cache and browsing history.
- Confirm whether you can make the problem happen again on demand, then note whether it happens on every page or only one, and whether it happens in the Console, the portal, or both.
- Note whether the problem follows you, with the same account on a different device or browser, or stays with the device, with a different account on the same device.
- If you use a VPN, try with and without it. Ask your IT team whether security software, web-filtering, or a local network setting such as DNS or IPv6 configuration could be blocking Rhythm; they may need to allow Rhythm's pages through.
Fix. Clear your browser's cache and cookies for the Rhythm site. In Chrome, use the lock icon next to the address bar to manage site data for just this site. Sign out of every open Console session, then sign back in. If the problem clears in a different browser, device, or network, keep using that one while your administrator or IT team looks at the original. If your organization's security software is blocking Rhythm, ask your local administrator to allow it.
8. A Broader Service Incident Is Underway
Why. Occasionally the infrastructure behind the Console, applications, and queries has a temporary problem that is not specific to your account, permissions, or browser. During an incident like this, you might see slow pages, timeouts, a Failed to contact the origin message, an error labeled Unknown Error that turns out to be a forbidden response underneath, errors submitting a web form, or even an Access Denied message on actions that normally work. Sometimes only some people are affected, while others who are already signed in keep working normally.
Check. Check Rhythm's public status page for a current incident. If other people at your organization, or at other organizations, see the same kind of failure at the same time, that also points to a broader incident rather than something specific to your account.
Fix. Wait and try again in a few minutes; refreshing the page sometimes restores access even while the incident is still being resolved. You can subscribe on the status page to get an email when an update is posted. Once the incident clears, access, application loading, and queries return to normal on their own, with no change needed from you.
9. A Recent Purchase Has Not Granted Access Yet
Why. After a purchase that includes a document or other digital library item, Rhythm normally grants access right away. Occasionally this does not happen, without a pattern that reliably explains why, so Support cannot always reproduce it from a description alone.
Check. Confirm the order completed successfully. If it did, but the item still does not appear in the person's library, the entitlement was probably never created for that specific purchase.
Fix. Ask your administrator to manually grant the missing entitlement in the Console instead of cancelling and recreating the order; this restores access immediately. Reprocessing the purchase as a new order also works if you prefer that route. Report the occurrence to Rhythm Support with the order details so a recurring pattern can be investigated.
When to Contact Support
Contact your administrator first for anything related to permissions. Contact Rhythm Support when:
- an application your organization has should be available but shows Application Disabled or Application Not Available;
- your administrator granted the permission named in the message, you waited five minutes, and the refusal continues.
Include your user name, the account or sandbox name from the top bar, the application, the page or button, the exact message with the permission name, and the time.
If the problem is intermittent and you cannot make it happen again on demand, open your browser's developer tools, usually with the F12 key, switch to the Console tab, and take a screenshot of any red error messages when the problem occurs. A short screen recording of the moment it happens also helps Rhythm Support investigate.
Some requests are handled by a specialized team for security reasons and can take longer than a typical fix. For example, removing an address from your account's email suppression list can take longer.