Skip to content

Administrator guide

This page is the day-to-day guide. For the rest of administration, start with the administration guide.

Administrator roles

  • Organization administrator — manages every tenant in the organization.
  • Tenant administrator — manages a single tenant: users, policies, connectors, and integrations.

User management

Invite users by email, assign them a role (Administrator or Viewer; see Roles and permissions), and, if your security policy requires it, force MFA activation. You can deactivate a user at any time; deactivation revokes their active sessions.

Tenant security policies

From Settings › Security and access › Security you control the access policy for every member of the tenant. Only the Administrator and the Organization administrator can see it (Roles and permissions):

  • Require multi-factor authentication. If you turn it on, every member must set up MFA to sign in. New tenants are created with MFA required; an administrator can switch it off. Turning it off is recorded in the audit log. SSO has its own rules.
  • Session timeout. Signs members out after a period of inactivity: 30 minutes, 1, 4 or 8 hours (the default and the maximum). The value applies to sessions already open, from their next request. A session can end up to about ten minutes before the chosen time, never after it. It applies to the tenant's members. The operators of its MSSP follow their own provider's policy. A member of several tenants gets the shortest timeout among them. Separately, no session lasts more than 8 hours from sign-in, however active it is.
  • Minimum password length. From 12 (the platform minimum, which no tenant can lower) to 128 characters. It applies when a member changes their password from My account, not on reset or when activating an invitation.
  • IP allowlist. One IPv4 address or CIDR range per line, up to 100 entries. With the list empty any address is allowed; with entries, only console sign-ins from those addresses are accepted, administrators included. API keys (and MSSP portfolio keys reading this tenant) are always held to the list: a key used from another address gets 403 IP_NOT_ALLOWED, and the refusal is recorded in the audit history. Connected applications (the CLI, MCP clients) are held to it while Apply the allowlist to CLI and MCP tokens is on, which is the default; turn it off only if a hosted MCP client reaches HodeiShield from its provider's network. Either way, approving a CLI or MCP sign-in in the browser checks your address. To keep you from locking yourself out, the console does not save a list that does not include your current IP.

Session and account

  • One session, one origin. The session cookie is only ever sent to the console's exact domain (app.hodeishield.com): it is never shared with any other subdomain, including third-party ones that might resolve under the same root domain. Signing out on one device ends that device's authentication immediately.
  • Suspending a tenant closes its sessions. If your organization suspends a tenant, or the whole organization, every account covered by that suspension loses its active session in the same act — not on the next sign-in attempt, but immediately. The next request from those accounts requires signing in again.
  • The console may show "service unavailable". Some console screens read their data through a dedicated internal service. If that service does not respond, the console does not silently degrade to partial or cross-tenant data: it shows a service-unavailable notice and asks you to retry, rather than risk an incorrect read.

Licensing and plan

Your tenant's plan determines which modules are available (compliance, FAIR/ALE, re-scan frequency…) and their usage limits. Check your license status under Settings › Organisation › Plan & Usage.

While your organization's beta is running, its tenants use the module set and limits of the Enterprise tier; the plan shown under Plan & Usage is still your commercial plan. To ask for support during the beta, write to info@hodeitek.com or use the Beta button in the console: we reply within 1 business day.

When the beta ends, converting to a paid plan is by sales contact: write to info@hodeitek.com with the subject "Conversión beta — your organisation" (the end-of-beta notices, the suspended-access screen and Settings › Organisation › Plan & Usage open it for you). We will send you an offer with the beta discount registered on your organisation and activate your licence; the beta is not subscribed to online.

Platform administrators who select modules above a tenant's licence tier see a refusal panel with the reason for each one; Save only the allowed ones saves the selection without the refused modules in one click (the server still rejects a list above the ceiling).

Publish your Trust Center

Your tenant's public Trust Center is managed under Settings › Privacy, trust and AI › Trust Center (/settings/trust-center). The page needs the supply risk module. Public and Unpublished visibility need no particular plan; Gated access (with allowed domains, NDA and access TTL), the custom domain and its verification need the Operate plan or higher, or the Trust Center attestation add-on, and the beta tier of your tenant includes it. The page has three tabs: Configuration, Access Requests and Audit Log.

  1. In Configuration, fill in Identity: Display name, Logo (Upload logo), Accent color, Tagline (up to 120 characters) and Hero description (up to 400).
  2. Choose what visitors see: Visible frameworks (if none is ticked, every activated framework is shown; a framework you have not activated never appears), Certifications, Subprocessors (the risk score is never published), Resources & documents, Data residency, Security contact and FAQ. Each document has a Category and a Visibility of Public, Gated or NDA only; gated documents download only after the visitor passes the access gate.
  3. Set the URL slug (lowercase letters, numbers and hyphens). It is required to publish, and the page tells you if it is taken or reserved. The Public URL field shows the final link.
  4. Pick the Visibility of the whole Trust Center:
    • Unpublished: not visible to anyone.
    • Public: anyone with the link can view it.
    • Gated: requires an approved access request. Under Gated access settings you can restrict Allowed email domains (empty allows any), set the Access TTL (days) of an approved token and turn on Require NDA acceptance with the NDA text.
  5. Click Save changes.

Visitors see the tabs Overview, Controls, Subprocessors, Resources and FAQ (see the visitor guide). Visitors can also use the floating Ask HodeiAI widget on the Trust Center, which is available during the beta.

For a Gated Trust Center, review requests in Access Requests: filter by Pending, Approved, Rejected or Revoked, and use Approve, Reject or Revoke on each. The Audit Log lists the access events: requested, approved, rejected, revoked, viewed and NDA accepted.

Custom domain

Serving the Trust Center from your own domain (for example trust.yourcompany.com) needs the same plan or add-on as Gated access, and a published Trust Center. Automatic certificate issuance is not available yet, so a custom domain is set up with the help of support: write to info@hodeitek.com with the domain you want to use.

The Custom domain panel on the Configuration tab lets you prepare the part that depends on you:

  1. Type the Domain and press Save domain. Domains under hodeishield.com are reserved and refused, and a domain already connected to another Trust Center returns an "already in use" message.
  2. The panel shows the CNAME target record and the TXT verification token. Create them at your DNS provider and press Verify: if the check fails, the panel says so and nothing changes.

Verifying the DNS is not enough for the domain to serve your Trust Center: support will confirm when it is live. Remove disconnects the domain immediately, after you confirm: the ownership token and the certificate are deleted, and reconnecting it means repeating the DNS records.

Embeddable badge

Once the Trust Center is published (Public or Gated), the Embeddable badge panel on the Configuration tab generates a live badge for your website or email signature. It has no plan of its own: it comes with the Trust Center.

  • Pick the Variant (Compact, Wide or Frameworks) and the Theme (Dark, Light or Auto); the Preview updates immediately.
  • Copy the snippet you need: Copy HTML, Copy Markdown, Copy URL or Copy PNG (email signature). If you publish frameworks, each one also gets its own badge with the same four buttons.
  • The badge carries a short reference to a cryptographically signed statement of your posture. Copy attestation URL gives you the link to share with anyone who asks how to check it: they download the signed document and verify the signature (ML-DSA-65). If image and document disagree, the document wins; the image is not proof by itself. To run the check with a tool, see the attestation verifier. The link expires: each attestation it returns is valid for 15 minutes, and never for more than one hour, so a copy saved earlier will show as expired. To get a fresh one, open the same link again (nothing has to be regenerated in the console) and ask the person you share it with to fetch it right before they verify.
  • What the attestation proves: that the posture has not changed since it was signed (integrity), that it was signed with HodeiShield's published key (origin) and the time HodeiShield stated when signing; it is valid for at most one hour. What it does not prove: it is not a certification or an audit, it does not replace either, it does not show that the data behind your posture is true, and it is not a qualified electronic signature or timestamp under eIDAS. Do not present it as any of these. Details: Evidential value.
  • If the Trust Center is not published, the panel only asks you to publish it. Embedding as an iframe appears disabled ("coming soon").

Subscribers

The Resources tab of the public Trust Center includes a form to subscribe to updates. It is double opt-in: the subscriber receives an email with a confirmation link valid for 3 days, and the subscription does not count until they press it. The form's response is always the same whether or not the address exists, so nobody can find out who is subscribed. Every subscriber can unsubscribe in one click from the link in the email, without signing in.

The console does not show the subscriber list to administrators and there is nothing to configure: sign-up and unsubscribing are handled by each visitor.

Summary for AI assistants (llms.txt)

HodeiShield publishes a plain-text summary of what a Trust Center contains, meant for crawlers and AI assistants, at /trust-center/llms.txt on the console's domain. It is generic: it describes the structure of a Trust Center and its access model (Public or Gated), and carries no tenant data. It is not configured from the panel.

Connectors

Integrate external tools (SIEM, ticketing, messaging) from Connectors in the sidebar (/connectors; Settings › Integrations and development › Integrations has a Go to connectors shortcut). Each connector defines what data enters and leaves HodeiShield, and is subject to the same tenant isolation as the rest of the platform.