When things go wrong
Situations people run into, and what to do.
This section is written for you to read when something doesn't go the way you expected. Each article starts from a real situation — a section you open turns out to be locked for you, a button is refused, a value is stopped by a floor, an invite expires, an install stays at “Installing” — and follows the same order.
Each situation has five headings: What happened, Why it happens, What inlorus does, What you do and So it doesn't happen again. Knowing the cause matters: in inlorus a refusal is usually not an error but a sign that a rule is working, and the rule also tells you what you can do.
If the screen you ran into shows a refusal text, you can also search for that exact text in the “Troubleshooting” section.
Articles in When things go wrong
- CaseA section is in the menu but opens lockedYou opened a section you see in the menu and the screen showed a lock and “You don't have access to this surface”. The menu group is open to you; that section's key is not.
- CaseA button is disabled, or was refused when pressedYou can see the screen but can't perform an action. Reading and changing are separate keys.
- CaseThe value I wrote in the tenant was refused: the higher scope's floorYou wanted to change a configuration value, and inlorus said the value cannot be weaker than the higher scope's. A floor can be tightened, not loosened.
- CaseThe invite link opens but has expiredYou opened the invite link you received and it says “The invite has expired”. Invites are valid for seven days; you need a new one.
- CaseThe invite says “This invite is not for you”You opened the invite link but you are signed in with a different email address. An invite can be accepted only with the address it was sent to.
- CaseA capability's install is stuck on “Installing”Install now runs the install right through to the end; the screen returns “Installed” or “Install failed” with its reason. An install stuck on “Installing” was interrupted, and the daily scheduled job continues it from where it stopped.
- CaseAn install failed, or never startedThe status became “Install failed”, or pressing Install gave a dependency error. inlorus states separately which step failed and which ones did not run because of it.
- CaseI signed in but no area opensThe menu and the home screen say “No area has been opened for you”. Signing in is not the same as having a place in a scope; a place comes with a membership and a role assignment.
- CaseThe capability I want to open is not in the Capabilities listThe builder says they built the capability, but it doesn't appear on the tenant's Capabilities screen. Drafts and other accounts' capabilities don't enter this list.
- CaseThe screen says “This screen works in a tenant scope”The screen you opened is for another scope. The console tells you the scope you are in right now; you switch to the right scope with the scope switcher.
- CaseI can't revoke someone's permission hereThe person carries a key in this tenant, but you can't revoke it on the Roles screen. The permission comes from a role given in a higher scope; that is where it is revoked.
- CaseI tried to give a role and it said “not a member”While giving someone a role or publishing rights, inlorus said they are not a member. A role is given only to someone who is already a member.
- CaseI have `config.write` but I can't change the configurationThe account's Configuration screen is read-only. Values can be written at the platform and in a tenant, not at an account.
- CaseI added someone to a team but they can't access anythingTeam membership alone grants no permission. A team records who works together; permission comes from roles.