Admin Guide
Everything a Super Admin or Org Admin needs to run BlockID: organizations, people, identities, tokens, and oversight. Administration happens in the dashboard at /dashboard.php.
Who does what
| Capability | Super Admin | Org Admin |
|---|---|---|
| Create / manage organizations | Yes | No |
| Manage users in their org | Yes (any org) | Yes (own org) |
| DID registry & schemas | Yes | Yes (own org) |
| API token management | Yes | Yes (own org) |
| Marketing admin (site, plans) | Yes | Limited |
| Platform-wide audit & ledger | Yes | Own org |
Organizations
Super Admin An organization is the top-level container. Every user, DID, schema, credential, token, and log belongs to exactly one organization, and BlockID enforces that boundary on every request.
Create an organization
Open Organizations → New, set a name and details, and save.
Assign an Org Admin
Create or promote a user to Org Admin and scope them to the org.
Monitor usage
Review credentials issued, active DIDs, and subscription status (see Subscriptions).
Users & roles
Manage people under Users. Each user has one of the five roles, which determines exactly what they can see and do.
Create a user
Users → New user, set name, email, role, and (Super Admin only) organization.
Apply least privilege
Grant the narrowest role that fits. Promote later if needed.
Deactivate when people leave
Disable accounts promptly. Their sessions end and access is revoked.
DID registry oversight
The DID Registry lists every decentralized identifier in the organization. As an admin you oversee which identities are allowed to sign credentials.
- Each DID is
did:blockid:{uuid}with an RSA-2048 keypair generated on creation. - The private key signs credentials and never leaves the server; the public key is what verifiers use.
- Keep the number of active issuing identities small and intentional — every DID is a trust anchor.
Marketing admin
Super Admin The marketing site is the application root (/). The marketing admin area lets you manage public-facing content and subscription plans. This is also where subscription statuses are reviewed and managed — see Subscriptions.
API token management
Super Admin Org Admin Open API Management to mint and manage tokens for programmatic access.
Create a token
Name it, pick its scopes, and optionally set an expiry.
Copy it once
The token is shown exactly once. BlockID stores only its SHA-256 hash — it cannot be shown again.
Scope to one organization
Every token is bound to a single org and rate-limited to 120 requests/min.
Revoke compromised tokens
Revoke instantly if a token leaks. All calls are logged for audit.
Audit & ledger integrity
Two complementary records keep you honest:
Audit log
A human-readable trail of sensitive actions — logins, user changes, token creation, issuance, revocation. Filter by user, action, and date.
Tamper-evident ledger
The hash-chained record of credential events. Run Verify Ledger Integrity to re-walk the chain and confirm nothing was altered.
Make Verify Ledger Integrity a routine — for example weekly, and after any database maintenance. A passing result confirms every link in the chain still matches.
Settings
Organization and platform settings cover branding, defaults, and security preferences. Pair these with the operational guides:
Security →
Hardening checklist, headers, RBAC, CSRF.
Deployment →
Server config, permissions, HTTPS, backups.
Troubleshooting →
Diagnose database and access errors.