MikroTik User Management per Site
Summary MKController Site User Management lets you add sub-accounts to a Site with either Admin (full access) or Collaborator (restricted access) permissions. Collaborator accounts can be scoped to specific functions, making it safe to give partners, technicians, or clients access to only what they need — without exposing your entire account.
What Is MKController Site User Management?
MKController Site User Management is the access control system that determines who can view and operate devices within a specific Site. Each Site can have multiple users with different permission levels, keeping your account secure while enabling delegation to technicians, partners, and clients.
Two permission levels are available:
| Role | Access scope |
|---|---|
| Admin | Full access to all devices and settings in the Site — identical to the account owner for that Site |
| Collaborator | Restricted access — you define which specific actions and sections are visible |
For ISPs: give resellers Collaborator access to the Site containing their CPE devices. They can see their devices and download vouchers without accessing other clients’ data.
For MSPs: give clients read-only Collaborator access to their Site so they can verify uptime and download availability reports independently.
For IT integrators: create Collaborator accounts for junior technicians scoped to the specific tasks they need — remote access but not backup deletion, for example.
How Do You Add a User to a Site?
Step 1: Open the Site Settings
-
Log in to app.mkcontroller.com.
-
In the left menu, go to Sites.
-
Find the Site where you want to add a user and click Settings.
Step 2: Add the User
-
In Settings, go to the Users section.
-
Click Add.
-
Fill in the required fields:
- Name: the user’s full name.
- Email: a valid email address. This becomes the login for the new account.
- Password: create a strong password (mix of uppercase, lowercase, numbers, and symbols). If this email already has an MKController account, the password field is ignored — the existing credentials are used.
Step 3: Set the Permission Level
Choose the appropriate access role:
- Admin: grants full access to the Site. Use for trusted team members and senior technicians.
- Collaborator: grants restricted access. After selecting Collaborator, define which specific actions the user can perform (remote access, backup download, voucher management, etc.).
Click Save to complete the process.
How Do You Remove or Update a User?
To change a user’s permission level or remove them from a Site, return to Sites → Settings → Users, find the user, and edit or delete their entry. Removing a user from a Site does not delete their MKController account — it only revokes their access to that specific Site.
Best Practices for Site User Management
Never share the account owner credentials. If a technician or partner needs access, always create a separate user account with the appropriate role. This preserves accountability and allows access to be revoked independently if the working relationship ends.
Use the Collaborator role for clients. Giving a client read-only access to their own Site — uptime reports, device status — reduces support calls and builds trust without exposing sensitive configuration data.
Audit user access periodically. When technicians leave the team or project engagements end, review the user list and remove accounts that are no longer needed. A dormant user account is a security liability even if it has limited permissions.
Create one account per person, not one per device. A user account in MKController represents a person, not a device. The same account can be added to multiple Sites with different permission levels on each.
Frequently Asked Questions
Can a Collaborator user see devices in other Sites? No. Collaborator access is scoped strictly to the Site they were invited to. They cannot view, access, or manage devices in any other Site on the account, even if the account has many Sites.
What happens to a user’s access if a device is transferred to another Site? Users with access to the original Site lose access to the transferred device once it moves. If they need access to the device in the new Site, they must be added to that Site separately.
Can the same email address have different roles in different Sites? Yes. A user with a single MKController login can be an Admin in one Site and a Collaborator in another. Each Site’s permission setting is independent.
Can a Collaborator create new devices or run the adoption script? Only if that specific permission is enabled for their Collaborator role. By default, Collaborators have view-only access unless you explicitly grant additional capabilities.
Questions about access control or permission levels? Contact MKController support on WhatsApp.