Skip to main content
Cedros

Why can’t I see or edit a feature?

Troubleshoot missing admin pages, read-only views, disabled buttons, permission errors, extension setup, and loading failures.

Use this guide when an admin page is missing, a button is disabled, or Cedros lets you view something but will not let you change it. Start with the symptom, then check the account, permissions, and setup that apply to that specific task.

A missing control does not automatically mean you need a more expensive plan or an Administrator role. Different causes need different fixes.

Start with what you see

What you seeCheck first
A page is missing from the sidebarThe site and account, collapsed navigation, page permissions, and required extensions.
A page opens, but controls are read-only or disabledThe message beside the control, your permission for that action, required fields, and any operation in progress.
One item is missing or cannot be editedThe selected view, filters, personal or shared scope, and access to that particular item.
A page shows an access-denied messageYour current sign-in, organization membership, and the page or action permissions.
A page remains loading or reports that it could not loadA loading or service problem; preserve unsaved work, then use the offered retry control.
The editor works, but visitors cannot see the resultWhether the correct revision is published and whether the page or site has visitor-access restrictions.

Record the exact message before changing settings. “The page is missing,” “the page is read-only,” and “the save failed” are useful distinctions when asking someone to help.

Check the site, account, and view

  1. Confirm the website address. The Cedros customer portal and an individual site’s admin are different places. Billing and account management in the portal do not use the same navigation as editing your website.
  2. Check the signed-in account and, where available, the selected organization. Use the account that accepted the team invitation for this site.
  3. Expand the relevant sidebar group or open the navigation menu on a narrow screen. Use admin search to look for the tool by name. Search helps you find available tools; it does not grant access to a hidden or restricted one.
  4. If the page opens but a record is missing, review search terms, status filters, and the selected personal or shared view. For example, personal Calendar work and team Calendar work are different scopes.
  5. If you recently joined or an owner changed your access, preserve any unsaved work and reload the admin. If Cedros asks you to sign in again, complete that sign-in with the intended account.

If the invitation is still pending, complete it before expecting team access. See Inviting teammates and accepting invitations.

For navigation help, see Finding your way around Cedros. If the problem is signing in rather than opening a feature, use Creating an account and signing in.

When a page is missing or access is denied

A site can limit access through your organization role, permission to use a particular tool, and restrictions on individual admin pages. These controls work together.

Ask an authorized site owner to check Users → Team → Manage Permissions for the page you need. They should confirm the saved rule and whether your account is among the people allowed to open it.

Being allowed to open a page does not grant every action on that page. For example, reading inbox messages, sending mail, and changing inbox settings have separate permission checks. Report the action you need, not just the page name.

Owners and administrators bypass ordinary admin page restrictions. An owner being able to open a page therefore does not prove that your non-admin account should be able to open it. Conversely, a role does not install an extension or make an unavailable feature appear.

Ask for the access your task requires

Give the owner a concrete request, such as: “I need to send replies from the shared inbox on this site. I can read messages, but Send is unavailable.” This is more useful than asking for all permissions.

Have the owner review the appropriate role, action permission, and page rule. See Choosing roles and managing permissions for the exact controls and their limits.

Do not use Remove restriction as a way to remove one person’s access; it opens the page to more teammates with admin access. Do not use someone else’s account or change a saved URL to work around a denial.

Check access to the specific item

If you can use the feature generally but only one record fails, check that record’s account, site, owner, and sharing or assignment settings where the feature provides them. Personal work, shared work, and records belonging to another organization can have different access rules.

Ask the owner of the item or the relevant administrator to review it. A broader organization role is not a substitute for identifying which record and scope caused the problem.

When a button is disabled or saving fails

Read the visible notice, field error, or explanatory text first. On desktop, a disabled control may also explain its requirement when you hover over it.

The page says it is read-only

Ask the owner to check the permission for the intended action. Some content screens can be viewed without permission to write content; a billing view can be readable without permission to manage billing.

If the interface shows a technical permission name, include that exact text in your request. You do not need to translate it into a role yourself.

The form is incomplete or busy

Complete required fields and correct any validation errors. Check that the intended item, account, mailbox, or subscription is selected. Wait for an operation already showing Saving…, Publishing…, or another in-progress state to finish.

A disabled Draft saved control can simply mean there are no unsaved changes. It does not, by itself, indicate a permission problem.

If a request finishes with an error, read the result before submitting again. For an uncertain payment, invitation, or other consequential action, check the current record first so you do not create a duplicate.

Saving works, but publishing is blocked

Review the publishing checks shown by that editor. A saved draft is not a published version, and unresolved review or readiness requirements may block publication even when editing is allowed.

Use Understanding drafts, previews, and publishing to check the current draft, preview, and public revision. Do not keep changing team permissions to solve a content-readiness problem.

Check feature setup and availability

Some features depend on an installed extension, a connected provider, or configuration on the particular site. Availability can differ between sites.

Review the required extension

An authorized administrator can open Settings → Extensions and find the extension under Installed Extensions. Check its status and any explanation or attention notice.

Installed and enabled are different states. The Extensions page can show an installed extension as Disabled, and features requiring an active extension may be absent until the owner resolves its state. An enabled extension can still have a page that fails to load.

Ask the administrator to review dependencies, access requests, compatibility, and any reported problem before making changes. Installing, enabling, approving, updating, or removing an extension affects the site; those actions are not routine diagnostic steps for every missing button.

If the feature is not offered for your site, ask the owner or support to confirm availability. A screenshot from another site or a general guide is not proof that the same feature is enabled in yours.

Complete the setup the page requests

Follow the specific setup notice or ask the administrator responsible for that connection. For example, team invitations can show Set up email to send invites with Open Email Settings when email setup is required.

Check the connected account, sender identity, or service configuration relevant to the action. A provider connection problem needs attention to that connection; granting a teammate a broader role does not repair it.

Avoid disconnecting a working provider or replacing a shared credential just to test a theory. First identify the failing operation and the message that explains it.

Check plan status or usage when the message points there

If Cedros reports a subscription, payment, or capacity problem, review the correct account’s Billing and Usage information. Confirm the service and scope involved, and distinguish a confirmed payment from capacity that is still being activated.

Missing, stale, or unavailable usage is not proof that the limit is zero. Do not purchase another plan solely because a feature is missing. See Managing your Cedros plan and billing for the supported checks and recovery steps.

When a page will not load

Messages such as Admin page couldn’t load or This section ran into a problem indicate a page-loading failure. They do not by themselves establish that your role is wrong.

Preserve unsaved work if you can, then select Try again when offered. You can also open another available section to see whether the problem is isolated to one page. If the page keeps failing, reload once and record whether the same error returns.

If every protected page returns you to sign-in, check your session and account first. If only one extension’s page fails, ask the administrator to inspect that extension’s status and version. Do not repeatedly disable or reinstall it as a first response.

An old bookmark may refer to a page that moved or is no longer available. Try opening the tool from the current sidebar or admin search. If it remains unavailable, send the old address and the tool name to support instead of guessing replacement routes.

Confirm the fix or ask for help

After the owner corrects the cause, reload using your own account and repeat the original task. Check both that the page opens and that the particular action is available. Use a draft or harmless check where possible, and confirm the saved result if the task requires a change.

If it still fails, send the owner or support:

  • The site address and selected organization.
  • The feature, item, and action you were trying to use.
  • Whether the page is missing, read-only, disabled, or failing after submission.
  • The exact error or requirement, when it occurred, and whether it previously worked.
  • The checks already completed, plus a screenshot with unrelated customer information and credentials removed.

If comparing with a teammate, have each person check from their own account. Do not share passwords, invitation links, recovery codes, or access tokens.

Use Getting help and reporting a problem for a complete support-report outline. If the issue is only that visitors cannot see your latest content, check the published revision and visitor-access settings before changing team access.