Appendices 13
Status Reference
Every status value in the product, what it means, and what it lets you do.
1. Member status
| Status | Label | Can sign in | Actions available |
|---|---|---|---|
| Active | 啟用中 | Yes | Deactivate · Reset MFA¹ · Copy · Log |
| Pending | 待處理 | No | Start · Send Email · Delete · Copy · Log |
| Inactive | 未啟用 | No | Unactivate · Delete · Copy · Log |
| Locked | 已鎖定 | No | Unlock · Reset MFA¹ · Delete · Copy · Log |
¹ Only when MFA Enabled is ON for that member.
Editing a member is not a status-dependent action — it happens inline on the detail page and needs member:U. There is no reset-password action for members.
Transitions
activation mail completed, or Start
Pending ───────────────────────────────────► Active
│ ▲
deactivate │ │ unactivate
▼ │
Inactive
Active ──── repeated failed sign-ins ────► Locked ──── unlock ────► Active2. Console administrator (User) status
| Status | Label | Buttons shown |
|---|---|---|
| ACTIVE | 啟用中 | Copy · Deactivate · Reset MFA · Log |
| INACTIVE | 未啟用 | Copy · Activate · Delete · Log |
| PENDING | 待處理 | Copy · Resend activation mail · Delete · Log |
| LOCKED | 已鎖定 | Copy · Unlock · Reset MFA · Delete · Log |
Import in modify mode allows only these transitions; anything else is a hard error:
Pending → Active
Active → Inactive
Inactive → Active
Locked → Active3. Application status
| Status | Label | Meaning | Actions |
|---|---|---|---|
| Active | 啟用中 | Running and reachable. | Detail · Copy · Deactivate · Flow Chart |
| Inactive | 未啟用 | Stopped, not reachable. | Detail · Copy · Activate · Delete · Flow Chart |
Delete is offered only on an inactive application, and there is no force-delete recovery path.
4. Application agentless status
| Status | Chip colour | Member-side effect |
|---|---|---|
| (off) | OFF | Not listed in the portal at all. |
| provisioning | Info | Card shows “preparing…”, button disabled. |
| active | Success | Card is openable, provided an access URL exists. |
| error | Danger | Card shows “preparing…”, button disabled. No retry — the backend re-drives provisioning itself. |
5. Device status
| Status | Can connect | Can be deleted | Notes |
|---|---|---|---|
| Normal | Yes | No | Registered and verified. |
| Inactive | No | Yes | Deactivating invalidates its tokens immediately. |
| Pending | No | No | Registered, awaiting verification. |
A member may register at most 5 devices.
6. Merak Node deployment status
| Status | Label | Bootstrap kit | Regenerate JWT | Meaning |
|---|---|---|---|---|
| PENDING | 等待佈署 | ✅ | ❌ | Created; the installer has not run. |
| PROVISIONING | 佈署中 | ✅ | ✅ | Installation in progress. |
| ONLINE | 已部署 | ❌ | ❌ | Enrolled and deployed. |
| OFFLINE | 未部署 | ✅ | ✅ | Not counted as deployed — currently unreachable. |
| ERROR | 錯誤 | ✅ | ✅ | Deployment failed. |
A node also carries a separate live connection status: ONLINE, OFFLINE or UNKNOWN (the last when the routing layer cannot be reached).
OFFLINEdoes not mean “already deployed”. It means the node is not reachable right now, so the installer and JWT regeneration stay available. It may be a node that never installed, or one that enrolled and has since gone down — check before re-runninginstall.sh.
7. Approval status
| Status | Label | Chip | Decision buttons |
|---|---|---|---|
| PENDING | 待審批 | Warning | Approve · Reject |
| APPROVED | 已解決 | Success | — |
| REJECTED | 已駁回 | Danger | — |
| CANCELLED | 已取消 | Default | — |
Batch approve and reject require every selected row to be PENDING.
8. Connection status
| Status | Chip | Closed at | Duration |
|---|---|---|---|
| open | Info | empty | computed live |
| active | Success | empty | computed live |
| closed | Default | set | final |
Lifecycle: open → active → closed. closed is terminal.
9. Audit log type and status
| Type | Meaning |
|---|---|
| Login | A sign-in event. |
| Action | An operation. |
| Error | An error. |
| Status | Chip |
|---|---|
| Success | Success |
| Failure | Warning |
| Error | Danger |
| Operator identity | Resolved from |
|---|---|
| Admin User | A Console user acted. |
| Member | A managed person acted. |
| Platform Admin | A platform administrator acted. |
| System | No human actor. |
10. Licence status and quota display
| Licence status | Chip |
|---|---|
| Active | Success |
| Expired | Danger |
| Suspended | Warning |
| Subscription plan | Values |
|---|---|
| Plan | POC · Basic · Pro · Enterprise · Custom |
Quota display rules (profile page, in this fixed order: Members → Applications → Devices → Merak Node → Agentless seats → Agentless services):
| Situation | Shown as | Usage bar |
|---|---|---|
| Has a limit | used / limit | Filled proportionally |
| No limit | used / Unlimited | Not filled |
| Not purchased (agentless seats only) | Not purchased | Not filled |
Bar colour: primary below 80 %, warning from 80 %, danger at 100 %. Over-quota clamps at full rather than overflowing.
A limit of zero means unlimited for every resource except agentless seats, where it means not purchased. Read the displayed label rather than inferring from the number.
11. Image status
Flag-gated; present only where the image feature is enabled.
| Status | Chip | Can be opened |
|---|---|---|
| ready | Success | Yes |
| processing | Info | No |
| failed | Danger | No |
Non-ready images can still be selected, tagged and deleted in bulk — they just cannot be opened.
12. Import row status
| Row state | Marker | Blocks submission |
|---|---|---|
| Valid | — | No |
| Warning | Amber dot + notice | No |
| Invalid | Red cell + message | Yes |
| Auto-corrected | Counted separately | No |
Warnings (never block): a duplicate display name; two rows targeting the same existing record in modify mode.
Errors (always block): an unresolvable enum, boolean or relation value; a failed field rule; an illegal status transition; more than 500 rows in the batch.