Users & access
Access in Makion has two parts: a person's global role (their overall access level on the server) and their per-project access (which projects they can actually work in). An administrator sets both. Most of this happens in the Admin tab; a project admin can manage their own project's members from the Members tab.
Global roles are access levels#
Every account has one global role, set in Admin → Project access via a Role select. Roles are levels, from least to most:
| Role | What it means |
|---|---|
| none — no access | The account exists but can do nothing yet. New accounts start here. |
| dev | Works in the projects they have been granted access to. |
| admin | Can manage the projects they administer — methodology, members, settings for those projects. |
| superadmin | Full server administrator: all projects, all users, engines, license, audit, and the Admin chat. |
The first person ever to sign in to a Makion instance automatically becomes the superadmin for the whole server. Everyone after that starts at none until an admin grants a role and project access. See Sign in & projects.
Granting access to a project#
A global role decides what level someone has; project access decides which projects they can open. Access is granted per developer, per project — there are two ways to do it.
As a superadmin (Admin → Project access)#
The Project access table in the Admin tab has one row per developer, showing their name and their email or Telegram identity. For each developer you can:
- Set the Role (none / dev / admin / superadmin).
- Tick the checkbox in each project column to grant that developer access to that project.
- Use Delete account to permanently remove the account (see below).
As a project admin (the Members tab)#
A project admin manages just their own project from its Members tab:
| Control | What it does |
|---|---|
| Current members | Lists everyone in the project, each with a role of Project admin or Developer. |
| Remove | Removes a member from this project. |
| Add a developer (select) + Add | Pick an existing account and add them to the project. |
Inviting people#
How you get a new person onto the server depends on how the server does sign-in.
Email + password servers — invite codes#
When the server offers email-and-password login, the Invite people section appears in the Admin tab. Fill in the form and issue a one-time code:
| Field / control | What it does |
|---|---|
| The invitee's email. | |
| Name (optional) | Their display name. |
| Role | The global role they'll get on joining. |
| Valid-for days | How long the invite stays usable. |
| Issue invite | Creates the invite and shows a one-time code box — "Shown once…" with Copy code. Send this code to the person. |
Below the form, an invites table lists each invite by Email, Role and Status (waiting / used / revoked / expired), with Revoke for any that are still pending. The invitee redeems the code on the sign-in screen — see Sign in & projects.
Telegram servers — self-login, then grant#
On a Telegram server there are no invite codes. The person simply logs in via the Makion bot (Telegram QR or the bot itself). Their account then appears at role none; an admin grants them a role and ticks the projects they may access in Project access. See the Telegram bot.
Deleting an account#
Delete account permanently removes a person's account. It is a link in each row of the Project access table, and it asks you to confirm — "Permanently delete {name}? … cannot be undone."
Deleting an account cannot be undone. As a safeguard, the Delete account link is hidden for yourself and for other superadmins — you cannot delete a fellow superadmin from this screen.
Login session length#
The Admin tab's Login session card sets how long a signed-in session lasts before a person must sign in again: enter a number of hours and click Save. This applies to everyone on the server.
Where to go next#
- Sign in & projects — the two sign-in methods and redeeming an invite.
- Configuring projects — set a project up before adding people to it.
- Telegram bot — signing in and working from Telegram.