How can we help?
A guide to every screen, fixes for the most common situations, and the reference behind all of it.
- UnderstandLearn the conceptsPlatform, account and tenant; capability, solution, role and permission — the ideas the product is built on.Start with the concepts
- Get work doneGuides by role and topicStep-by-step guides for every screen and every task.Find a guide
- Solve a problemWhen things go wrongSituations people run into, error messages and quick fixes.Find a fix
About this help center
This help center is written for everyone who uses inlorus: people who run the platform, who run an account and its tenants, who build capabilities, who watch the running systems, who audit access, and who use the product for their daily work. What you see in inlorus depends on two things: which scope you are in (platform, account or tenant) and which role you hold in that scope. Everything here is built on those two ideas.
You can find what you need in three ways. By your role: each role has a five-step “Start here” path and the articles it uses most. By your situation: the “When things go wrong” section describes situations people actually run into — a menu that won't open, a refused action, a value stopped by a floor, an expired invite — and tells you what to do in each. By topic: a guide for every screen, step-by-step articles for common tasks, concepts that explain why the product works the way it does, and complete lists.
Screen guides are the same text you see in the Help panel in the app; the two never say different things. Every article describes what inlorus does today; none of them makes a promise about a future release.
Every article ends by taking you to the next step: the related screen in the app or another related article. If an action was refused, look at the “Troubleshooting” section first: the refusal texts inlorus shows are written out there one by one, with their causes and fixes.
Start with your role
- Platform administrator“What does each role grant, and what can the scopes below me not relax?”Start here
- Builder“How does a capability I build reach a tenant?”Start here
- Account administrator“How do I manage my tenants, and who can do what in them, from one place?”Start here
- Tenant administrator“How do I add someone, what can they do, and how do I open a capability?”Start here
- Operator“What is broken right now, and who is on it?”Start here
- Auditor“Where does this person get this permission from?”Start here
- Member“Where are my applications, and why can't I see some things?”Start here
Browse by topic
- Getting startedSigning in for the first time, the home screen, first run and accepting an invite.5 articles
- ConceptsPlatform, account and tenant; capability, solution, role and permission — the ideas the product is built on.6 articles
- My account and securityYour own account: sign-in, two-step verification, sessions, your access, your activity and your preferences.10 articles
- StudioDefining capabilities, packaging them as solutions, publishing them and opening them in a tenant.18 articles
- Applications and dataOpening an application from the catalog, workspaces, Explorer and flow boards.13 articles
- Platform governanceAccounts, identity and access, policies, security, configuration and integrations.7 articles
- Account governanceAn account's tenants, roles, policies, security, configuration and entitlements.8 articles
- Tenant governanceMembers, roles, access, teams, configuration, data governance, domain and applications.12 articles
- Tenant designData schema, views, workflows and actions — where a tenant's applications are built.5 articles
- OperationsComponent health, service objectives and incidents.3 articles
- AuditWho can access what, and why; what a change touches.3 articles
- When things go wrongSituations people run into, and what to do.14 articles
- TroubleshootingError messages and refused actions, with the cause and the fix.8 articles
- ReferenceScopes, archetypes, the permission glossary and statuses in one place.5 articles
When things go wrong
- “A section is in the menu but opens locked”You 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.
- “A button is disabled, or was refused when pressed”You can see the screen but can't perform an action. Reading and changing are separate keys.
- “I signed in but no area opens”The 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.
- “The value I wrote in the tenant was refused: the higher scope's floor”You 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.
- “The invite link opens but has expired”You opened the invite link you received and it says “The invite has expired”. Invites are valid for seven days; you need a new one.
- “A 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.
- “The 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.
Error messages and quick fixes
- “You don't have access to this surface”The screen opened, but instead of the content you see a lock and a missing key. You don't hold that key in this scope; the screen also says who can grant it.
- `NOT_PERMITTED: … default_deny_no_matching_rule`You pressed a button and the action was refused with this code. The line tells you the missing key and the scope the action was requested in.
- “… cannot be weaker than the scope above's value”The configuration value you wrote in the tenant was refused because it is looser than the floor set by the scope above.
- The invite page doesn't show an accept buttonYou opened the invite link and one of four headings appeared. Each one tells you a different cause.
- “This screen works in a tenant scope” and similarThe screen you opened is for another scope. It tells you the console's current scope and the one the screen needs.
Still stuck?
Write to info@projera.com with the affected account or tenant, roughly when it happened and what you saw. Don't send passwords, access keys or payment details; we will never ask for them.