Sekia can read files, run commands and make changes in your business apps. Here is how each of those stays under the control of the person using it and the admin who runs the workspace.
The Mac app shows the exact command, file or click before it runs. The person chooses Allow, Deny, or allow one app for the rest of that chat.
Keychain Access, Passwords, 1Password, Bitwarden, LastPass, Dashlane and System Settings always ask, every time.
An "allow this app in this chat" approval ends after 24 hours idle, when it's revoked, or when remote control is turned off.
Admins set each connected-app action to Allow, Ask first or Blocked, with overrides by role and by person. Blocked actions are hidden from the assistant.
People connect apps with their own login, so the assistant sees only what they could see. Shared logins start blocked for any action that changes data.
People sign in with a link sent to their work email. On the Mac, the session is stored encrypted with a key held in the macOS Keychain.
Every connected-app call and Mac action is recorded with the person, the action and the decision.
Every release is signed with an Apple Developer ID and notarized by Apple. Updates install only if the signature matches.
The interface runs sandboxed with no direct network or file access. All requests go through the app's core, and generated content renders on a separate origin.
Accessibility and Screen Recording stay off until you allow them in System Settings, and the app tells you which actions need them.
Create a workspace, add an app, and set its permissions. It takes a few minutes.