Admin overview
An administrator sets Makion up so it works the way your team works: which projects exist, which SAP systems they target, which AI engine runs each one, who can use them, and the standards the agent must follow. This page is the hub — it says what an admin does and links to the page for each surface.
Most admin surfaces are visible only to a superadmin. Some project-level tasks can also be done by a project admin — the person who created a project or was given the admin role on it. See Users & access for the difference.
Where admin work happens#
| Surface | Nav | Who sees it | What you do there |
|---|---|---|---|
| Admin tab | Admin | Superadmin | Set the login-session length, configure each project (SAP system, ABAP flavor, engine, autonomous), connect AI engines, grant per-project access, invite people. |
| Methodology tab | Methodology | Project admin / superadmin | Set the base rules, per-role methodologies, and knowledge base that steer the agent. See Methodology. |
| Admin chat | Admin chat | Superadmin | Configure the server in plain language — create projects, grant access, edit rules. |
| Retro | Admin chat → Proposals | Superadmin | Review and apply improvements Makion proposes from past mistakes. |
| Audit | Audit | Superadmin | Read the immutable trail of who connected and what was done in SAP. |
| Settings → License / Updates | Settings | Superadmin | Activate a license and install app / server updates. See Settings. |
The pages in this section#
- Configuring projects — the key page: how to set a project up so Makion follows your team's exact instructions when it builds code or acts in SAP.
- Users & access — the access model, inviting people, granting project access, and deleting accounts.
- AI engines & login — pick an engine per project and authenticate it with a subscription or an API key.
- Admin chat — configure the server in natural language.
- Retro — learning from mistakes — review and apply the agent's self-proposed fixes.
- Audit trail — the accountability backbone: every connection and SAP action.
- License & updates — activate a license and keep the app and server current.
The first thing to do#
The first person ever to sign in to a Makion instance becomes the superadmin for the whole server — see Sign in & projects. From there, the usual order is:
- Activate a license — License & updates.
- Connect an AI engine — AI engines & login.
- Create and configure a project — Configuring projects.
- Add your developers — Users & access.
Makion never changes SAP on its own. Admin work is about steering how the agent works and who may run it — not about loosening the human-in-the-loop guarantees. Those are described in the Security model.