Settings
Access settings under Settings (gear icon in the sidebar footer).
The Settings screen (Admin and Super Admin) has the tabs Organisation, Profile, Security, Notifications, Risks, SSO, Integrations, Data and AI, Privacy, Appearance, Billing and, for Admin and Super Admin only, White-label. Member and role management is in People → Access (below).
General Tab
- Organisation / tenant name
- Logo
- Description
- Active frameworks
Billing Tab
Shows the current plan and, when a subscription exists, the access to manage it. If your organisation's plan and conditions are managed by the EterShield team under the organisation's agreement (no paid subscription linked), this page has no payment buttons and the change is handled by the team. In those cases an Admin clicks Request a plan change; the request is recorded in the organisation's audit log and the team replies by email. You can send up to 3 requests per hour.
Members Tab
Member management is done in People → Access, MEMBERS tab (the ROLES tab manages roles per entity).
Inviting a new member:
- Click Invite Member
- Enter the email
- Select the role (Admin / Manager / Viewer, or a custom role)
- Optionally, restrict the invitation to one entity ("Restrict to one entity") and choose the role on that entity
- Click Send Invitation
The user will receive an email with an activation link.
Inviting someone who already has an account in another organisation. The invitation is sent in the same way. The recipient sees the "Accept invitation" screen, which states that the email already has an EterShield account: they must accept with the session of that account (if they have not signed in yet, they go to the login and then return to the invitation). No new account or new password is created: the person gains access to one more organisation and switches between them as described in section 1. If your organisation has turned off "Accept external members" (see Security Tab), the invitation is refused.
External members. In People → Access → MEMBERS, anyone whose account is in another organisation appears with the label "External · name of home organisation". The account belongs to that organisation; from here you manage only membership of your organisation: deactivating or deleting an external member removes their access to your organisation, but does not affect the account or the other organisations they belong to. External members always sign in with a second factor.
Available roles:
| Role | Permissions |
|---|---|
| Admin | Full access, can manage members and settings |
| Manager | Create and edit all records |
| Viewer | Read-only |
Security Tab
In Settings → Security you configure your personal second factor (MFA: Set up / Disable). Administrators also see two organisation panels below it.
Security policy (Admin only). Organisation rules for the second factor and for sessions. They add to the platform's rules: they can tighten them, never relax them. Click Save policy to apply: open sessions start respecting it within the next minute.
| Setting | Options / values |
|---|---|
| Second factor (MFA) required | Follows the platform default · Off · All administrators · All users: anyone who does not yet have a second factor is taken to set one up at their next sign-in. "Follows the platform default" is different from "Off": it is the absence of a choice, and follows the platform rule (administrators required from 23 November 2026). Saving other policy settings does not change this choice |
| Accept external members | Allows accounts from another EterShield organisation (e.g. the consultant who supports you) to enter by invitation, always with a second factor. When off, invitations and SCIM refuse them and anyone who is already external can no longer sign in |
| Expire after inactivity (minutes) | Between 5 and 480; empty = no limit of its own. The session ends on the server, not only in the browser |
| Maximum session duration (hours) | Between 1 and 168; empty = 7 days (platform). Forces a new login, even with activity |
With no saved policy, the second factor is required for administrators from 23 November 2026 (Monday, 00:00 Lisbon time): from then on, at their next sign-in, anyone who does not yet have one is taken to set it up. Until then, with no saved policy, it is not required. The organisation can choose Off to waive it. An organisation that never chose anything stays on "Follows the platform default". After 5 wrong codes in 15 minutes, verifications stay blocked until the window ends.
Anyone who signs in through the organisation's SSO is subject to the MFA of the respective identity provider: the EterShield second factor is skipped only if that provider proves that MFA was done in that session (see section 1, "Confirming the email and sign-in limits").
Under Recovery codes you can see how many recovery codes for the second factor remain and generate new ones (the previous ones stop working).
Resetting a member's second factor. If someone lost their phone and their recovery codes, an administrator can reset their second factor in People → Access → MEMBERS, with the Reset 2FA button. To confirm their identity, the administrator enters a current code from their own factor (a recovery code does not work), so they must have their own second factor enabled. You can only reset the account of someone whose role is equal to or lower than the administrator's, and not that of external members (the account belongs to the home organisation). Open sessions of that account end.
Segregation of duties in approvals (Admin only). Defines what happens when the same person who submitted, created or owns a record tries to approve it. It applies to policies, control exceptions, minutes, quality documents, management reviews and supplier assessments; in an access review, nobody certifies their own access.
| Mode | Effect |
|---|---|
| Log (recommended to start with) | Lets it through, but logs in the SOC every approval made by the same person who submitted |
| Mandatory | Refuses the approval with the message "Segregation of duties: the person who submitted or created this record cannot approve it. Ask another person with permission." |
| Off | Does not check. Only for organisations with a single responsible person |
Warning: with Mandatory, make sure there are at least two people with permission to approve: with a single administrator, approvals are blocked.
SSO Tab
SAML 2.0 authentication configuration for enterprise SSO (Admin only):
- IdP Entity ID (must be identical to the issuer the identity provider sends in its responses)
- SSO URL
- X.509 certificate
- Email domains for auto-provisioning
Access always starts in EterShield (the SSO (company) field on the sign-in screen). Signing in from the identity provider's app panel is not supported: EterShield only accepts responses to a request it sent itself.
Proof of email domains. For SSO, automatic provisioning (JIT) and SCIM to apply to a domain, the organisation must prove that the domain is its own. Below the SAML configuration, the Email domain proof card shows, for each domain listed under Email domains, the record to publish in DNS:
- Add the domains and save the configuration; click Generate record (if one does not exist yet) to see the Type, the Record name and the Record value (a TXT record)
- Publish the TXT record in the domain's DNS and click Verify
- The status changes from Pending to Verified ("Verified on" and the date). If it fails, the message explains why: record not found (DNS may take time to propagate), value that does not match (copy the full value), domain already verified by another organisation, or DNS unavailable
Without this proof the domain activates nothing. The proof is rechecked every day: if the TXT record disappears or stops matching, the domain is flagged and, if the failure repeats the next day, it becomes Failed, SSO, JIT and SCIM stop applying to that domain and every administrator receives an in-app notice. A temporary DNS error does not revoke the proof. If you remove a domain from the list, its proof is released and you can prove the same domain again without a new record. SSO and SCIM are included in the subscription (not in the demonstration period).
Your organisation's SSO only authenticates accounts of this organisation. An account that belongs to another organisation (for example, an external consultant) is refused at login with the message "This account belongs to another organisation. Sign in with the email and password (or SSO) of your organisation: access to this organisation becomes available afterwards." Those members sign in through their own organisation and use the selector described in section 1.
SCIM provisioning (Entra ID, Okta). Below the SAML configuration, the "SCIM provisioning (Entra ID, Okta)" card lets the organisation's identity provider automatically create, update and deactivate accounts and groups (departments):
- Copy the Tenant URL with the copy button
- Click Generate SCIM token and copy the token: it is shown only once; it is revoked in the API keys list
- Paste the two values into the IdP's provisioning configuration
The token only works for SCIM. The groups mapped in "Role per group" define the role of anyone created through SCIM. Deactivating an account in the IdP ends that account's sessions in under a minute; the last administrator is never deactivated.
Integrations Tab
The ADMIN and SUPER_ADMIN roles also have an Integrations entry in the side menu, which leads directly to this tab (Settings, integrations tab).
Configure integrations with external tools:
| Integration | What it is for |
|---|---|
| Wazuh | Import security alerts and findings from the EterSOC SIEM (see section 40) |
| GLPI | Synchronise the computer inventory and create a remediation ticket from a gap (GLPI button on the gap) |
| EterScan | Vulnerability scanner |
| GitHub | Development posture connector: fields: Organisation, PAT Token; automatic pull sync every 60 min |
| Google Workspace | Identity posture connector: Admin SDK (users, groups, MFA, security policies) |
| Microsoft 365 / Entra ID | Identity posture connector: fields: Tenant ID, Client ID, Client Secret; sync via Microsoft Graph |
| Microsoft 365: accounts and licences (write) | Dedicated application in Entra ID, separate from the read one, for the automatic steps of the JML processes and for licences (sections 28.1 and 52). ADMIN and SUPER_ADMIN only |
| Fleet | Read-only managed devices (MDM): serial number, system, encryption and compliance (section 52). ADMIN and SUPER_ADMIN only |
| GCP | Cloud security posture connector (Google Cloud Platform) |
| AWS | Cloud security posture connector (Amazon Web Services) |
| Azure | Cloud security posture connector (Microsoft Azure) |
| Okta | Identity connector (IdP) |
| OpenCTI | Threat intelligence integration |
| Prowler | Import of cloud security audit findings |
| Jira | Send tasks to Jira automatically and receive the status of issues by webhook |
| CNCS | Connector with the National Cybersecurity Centre (Portugal) |
Suricata and backup report: network alerts and backup status arrive through keyed ingestion points (see the API reference), not through a card in the integrations list. Notifications to Slack and Microsoft Teams are set up in the notifications tab.
For each integration: endpoint URL, API key/credentials, synchronisation interval and a Test Connection button. Synchronisation is periodic and automatic (see section 39). For security, an integration's address must be public and start with https://; local and private-network addresses are refused. If your tool is on a private network, ask the EterShield team to authorise it.
API Keys
For external integrations (EtherFlow, automations), generate API keys in the integrations tab. Keys are shown only once, so store them securely. Per-integration keys must have at least one allowed route: it is no longer possible to create a key without routes. If the organisation has old keys without routes, the card shows a warning with the deadline (when set); revoke them and create new ones with the routes the integration needs. The key authenticates by hash and is no longer sent in the address.
19.1 Settings > Knowledge Base (Documents)
The Knowledge Base section in Settings lets you upload documents that feed the RAG (Vera's context) at tenant level.
Supported formats: PDF, DOCX, TXT, CSV (max. 10 MB per file)
How to upload:
- Go to Settings → Knowledge Base
- Drag the file into the drop zone or click to select
- The system extracts the text, splits it into chunks (1500 chars / 200 overlap) and indexes it automatically
- The status changes from PROCESSING → READY (automatic polling every 3s)
Document list: shows name, size, date, number of chunks and status. To remove one, click the bin icon and confirm.
This KB is different from the per-entity Knowledge Base (Knowledge tab). The documents uploaded here are available to the whole tenant, not just to a specific entity.
19.2 Data and AI: the organisation's AI and "Where is my data"
The Data and AI tab in Settings brings together everything about where the data is kept and the organisation's AI. The Where is my data card is always visible. Using your own AI provider, storing files in your own storage and having your own database will be available soon.
Organisation AI. The administrator can turn off all AI for the organisation, and turn it on again, in the Organisation AI card. With AI turned off, no AI feature sends data to any AI service. The change is recorded in the audit log and only administrators can make it. In the Manager view the texts are simpler ("Artificial intelligence").
How AI works. AI answers (Vera, "Suggest with AI", Cook, executive report, supplier analysis, document reading, etc.) go through the Eter AI service, with personal data masked before it goes to the model. Images (for example, OCR of evidence) cannot be masked.
- AI turned off for this organisation. No AI feature makes calls: Vera, gap analysis, form suggestions, Cook, OCR and supplier analysis become unavailable and users see "AI turned off for this organisation". No data is sent to the Eter AI service or to any provider. It is always respected, in every AI feature. To turn it on again, use the Turn AI on button in the Organisation AI card.
- Account suspension and the end of the demonstration period still block AI.
Where is my data (any user). Information card with the location of the database, the files, the evidence retention and the AI:
| Option | Meaning |
|---|---|
| EterShield (default) | The database is shared on Eter servers, in the European Union (EU, dedicated server in France), and isolated per organisation |
19.3 AI usage
The AI usage page (menu, Control section; Admin and Manager) shows the organisation's AI use during the month: form suggestions, AI credits and estimated cost (at public prices, indicative), broken down by type of operation (calls, credits, tokens and cost) and suggestions per user (reused ones do not count towards the quota).
What an AI credit is. The monthly AI quota is counted in credits, not in calls. A normal AI operation (analysing a gap, generating a report, reading a document, each answer step of Vera, and one question can have more than one step) spends 1 credit. A heavy operation spends 3 credits: today, generating ten policies at once in Fill with AI.
What does not spend credits.
- Tasks the platform does by itself, with nobody asking: linking integration findings to controls after each synchronisation, the regulatory watch and batch document reading. They have a daily protection limit; if it is reached, that task is postponed to the next day and nothing you asked for is affected.
- Form suggestions ("Suggest with AI"), which have their own quota.
When credits run out, AI refuses the request with the message "AI credits exhausted" and the rest of the platform keeps working. A heavy operation needs 3 free credits: 1 or 2 credits may be left and the heavy operation refused, while a normal one still goes through. The Credits column of the breakdown shows how much each type of operation spent, and the sum is what counts towards the limit.