積載

Platform Security and Access

Actualog separates signing in from permission to use a particular company's information or perform a business action. An account identifies the person; roles, resource scope, delegated authority and record state determine what that person can do.

This article explains the application boundaries relevant to users, administrators and IT reviewers. Deployment controls such as network restrictions, backup retention, data residency and recovery objectives must be confirmed for the environment under review.

Accounts and browser sessions

Interactive sign-in uses ASP.NET Core Identity. The browser carries the protected application session cookie; ordinary browser editing does not require a company API secret. Password, external-provider, authenticator, recovery and passkey flows use the framework's account lifecycle.

E-mail confirmation establishes control of an address. It does not make the account a Company Administrator or approve an invitation without the applicable checks. Keep account addresses current and use the normal confirmation and recovery forms. See E-mails.

Use your own account for attributable work. Sign out on shared computers, protect the mailbox used for recovery, and avoid sharing a browser profile with another operator. If a session expires, sign in through Actualog before repeating the intended action.

Two-factor authentication and sensitive actions

Actualog requires MFA for application roles and permission-bearing company roles. A read-only role can still require MFA when it grants access to non-public information. The normal methods include authenticator codes and recovery codes, with passkey sign-in available through the account security workflow.

A trusted browser can reduce repeated authenticator prompts. It does not grant business permissions, and sensitive operations can require fresh verification. Clearing site cookies or using another browser profile can trigger a new sign-in challenge.

Register recovery methods before they are needed and store recovery codes privately. For setup, supported methods and browser behavior, see Two-factor authentication. Administrators should verify the actual MFA flow in the target environment; a local development convenience setting is not evidence of production security behavior.

Company context, roles and mandates

One person may belong to several companies and hold different responsibilities in each. Selecting a company changes the working context; it does not transfer authority from another company. The server checks the requested company and resource rather than trusting a company identifier submitted by the browser.

Company roles govern activities such as maintaining product data, approving releases, managing integrations or publishing passports. Preparation, approval and publication are separate responsibilities. Give people the responsibilities they need and review membership when contracts or employment change. See User management.

An Operational Delegation records a mandate for a named user or partner company. Its recipient, acceptance, dates, activity and resource restrictions must match the operation. Authority for one batch does not authorize another batch. A partner company's staff still need the appropriate company responsibilities.

Platform administration does not replace a company mandate for operational actions or create independently verified regulatory authority. See Operational delegations.

Public API credentials and delegated agents

These integration paths have different purposes:

Access path Identity and authority
Browser application The signed-in user's Identity session, roles and resource permissions.
Public API Company credentials linked to a user and company, with the public API's permissions and plan admission.
MCP agent connection A user's OAuth delegation, approved scopes, current account authority and native tool checks.

Company API credentials use a Client ID and secret. They are accepted on explicitly designated public integration endpoints and cannot be used as a shortcut into internal or Admin endpoints. Membership and company scope remain relevant. Keep secrets in protected server-side storage, rotate them when required, and never place them in public code or browser scripts. See API Key Management.

MCP uses the supplied environment and supported client connection settings, native sign-in, applicable MFA and consent. Delegated access is available to authorized users for the roles, company context and operations they approve. Connecting an agent does not require granting it platform administration or unrestricted company access.

Start an agent connection with a read-only task and check the actual connection context. Reading does not authorize changes: category and reference-dictionary write scopes require their own approval, and a permitted tool still applies the native domain rules. See Actualog MCP and Connect your agent to Actualog.

Public information and protected files

Actualog supports intentionally public information, including selected company profile media, alongside protected company workspaces and restricted document evidence. A public preview and a Media Assets management screen serve different audiences.

Review the placement and intended audience before publishing a file. Treat a public file as information that recipients may retain or redistribute. An unpublished working record is not a substitute for checking every file's exposure.

Retained document revisions and passport publications have their own subject and audience rules. Permission to manage the current media library does not mean every recipient can read every retained evidence file. See Media Assets and Retained document revisions.

Server-side checks and practical review

Commands validate authority, business rules and relevant record versions on the server. Browser forms and cookie-authenticated JSON commands use request verification tokens for changes. Concurrent changes can require a new review rather than applying an older decision to changed data.

For an IT review, confirm the following in the intended environment:

  • account, MFA, recovery and external-provider configuration;
  • company membership, assigned roles and current delegated mandates;
  • public pages and file audiences, including a signed-out check;
  • API credential ownership, approved agent scopes and enabled services;
  • transport and network controls, secret storage, logging, backup and recovery arrangements.

Application features alone do not establish a certification, legal compliance status or service-level commitment. Those conclusions need the applicable deployment evidence and organizational review.