Team & accounts
Members, roles, tenants and solution settings.
CorPole is organised as account, tenant, solution and record. An account is the organisation; tenants are its units, each with its own members, solutions, settings and knowledge, and a Portfolio board of demands and initiatives; solutions hold the records, the design and the work. What is set higher up — standards, glossary terms, the agent policy baseline, drift thresholds, roles — applies below.
Access has two layers. A tenant access level says how far someone reaches: owner, admin, auditor, member or viewer. Solution roles — product owner, business analyst, architect, developer, tester, risk owner, project lead, or your account's own — say what they may do inside a solution, and a person's permissions are the union of their roles. An agent never exceeds the person it acts for.
Some decisions need two people. Maker-checker lets you require that the person who asks for a task cannot approve it and the person who carried it out cannot check it; agents never approve or check.
The articles here explain the structure, how to invite people and give them roles, how maker-checker works, and the account, members and settings screens.
Articles in Team & accounts
- GuideProduct feedbackRequest a feature, suggest an improvement or report a bug, and read replies from the product team.
- GuideAccess reviewWho can reach what in the tenant: members with their roles and solution access, and every agent credential with its scopes, last use and end date. Unused, never-used, open-ended and orphaned credentials are flagged; for one person it shows what breaks when they leave. The review itself is recorded.
- GuideTime reportYour coding-agent time by day and solution, for an invoice or a weekly report, and the solution's day totals without names.
- GuideMaturity settingsHow strictly the solutions under this platform, account or tenant are measured on the Maturity screen: thresholds, dimensions, conditions, method, target profiles and where maturity shows.
- GuideMembersThe people in this tenant, their access level, the team of the active solution with its roles, and an access review.
- GuideAccountThe account is the organisation above the tenants, e.g. a bank with its business units or subsidiaries as tenants. What is set at account level applies to every tenant.
- GuideGovernance across the accountFor account owners and admins: one view of how the tenants and solutions of the account keep to its line.
- GuideOption listsThe categories offered in forms and to agents — for risks, standards, lessons, ideas, agent rules and tasks — changed for the account or a tenant without changing the code.
- GuideMy ideasA private place for ideas you are not sure about yet. Only you see them; nothing is counted, shared or turned into a demand unless you decide.
- GuideRoadmap indicatorsFor platform admins: whether each roadmap wave's leading indicator holds and whether a stop threshold is crossed, read in one tenant — the gate for the next wave.
- GuideAgent benchmarkFor platform admins: how CorPole changes coding agents' cost and correctness, compared with requirements kept as markdown in the repository — suite by suite.
- GuideSecurityFor platform admins: how robust CorPole's security is — each security suite's latest run, what is new or fixed, and the trend.
- GuideAI usageFor platform admins: the calls CorPole's own AI features made to the model, per tenant and per feature, with their tokens.
- GuideFeaturesFor platform admins: the flags that bring big changes to people step by step — first chosen people and sandboxes, then everyone.
- GuideYour themeChange any setting of the platform theme for yourself, see it in the preview, then save it in this browser.
- GuideThemeFor platform admins: the one theme every tenant sees, set at runtime without a deploy.
- GuideTenant settingsTenant-wide rules for all solutions. Owners and admins can change them. Open it from ⚙ in the top bar.
- GuideYouYour own page: profile, the tenants you belong to, your agents, and how CorPole reaches you. Open it from your initials at the right of the top bar.
- ConceptAccounts, tenants and solutionsAccount → Tenant → Solution → Component. What is set higher up applies below; initiatives carry the work.
- ConceptAccess levels and solution rolesA tenant access level says how far someone reaches; solution roles say what they may do in a solution.
- ConceptMaker-checker: a second person approvesThe person who asks cannot approve, and the person who did it cannot check it. Agents never approve or check.