Skip to main content

ArkBox Vault

ArkBox Vault provides secure, centralized file access by connecting storage from ArkBox agents and exposing selected folders as controlled shared spaces.

What ArkBox Vault Is For​

Use ArkBox Vault when teams need shared access to project files, documents, or resources stored on connected systems.

Vault helps users avoid:

  • Manual file sharing.
  • Separate access-control processes.
  • External storage tools for internal project files.

Core Concepts​

ConceptMeaning
AgentA connected machine or server that can host storage.
Vault ShareA selected folder from an agent that is made available to users.
Access ControlRules that decide which groups can see a share and what actions they can perform.

My Vault​

My Vault is the user access area.

Users can:

  • View assigned vault shares.
  • Browse files and folders.
  • Download files when allowed.
  • Upload or modify content when allowed.
  • Delete files when delete permission is granted.

Configure Vault​

Configure Vault is for administrators.

Administrators can:

  • View available agents.
  • Review agent hostname, IP address, operating system, and storage details.
  • Add new shares from agent folders.
  • Assign groups to shares.
  • Set allowed actions such as read, write, download, and delete.
  • Review existing shares and user access.

Create A Vault Share​

  1. Open ArkBox Vault from the top navigation.
  2. Go to Configure Vault.
  3. Select an available agent.
  4. Review the storage locations shown for that agent.
  5. Select Add Share.
  6. Choose the folder path to expose.
  7. Enter a clear share name.
  8. Assign user groups.
  9. Select the permissions those groups should have.
  10. Save the share configuration.

Access A Vault Share​

  1. Open ArkBox Vault.
  2. Go to My Vault.
  3. Select an assigned vault share.
  4. Browse to the needed folder or file.
  5. Use the available actions shown for your permission level.

Security Model​

  • Storage is not exposed by default.
  • Every share must be created intentionally.
  • Access is granted through groups.
  • Permissions define what users can do inside a share.
  • Users only see shares assigned to them.

Good Practices​

  • Use descriptive share names, such as Project Media or Translation Drafts.
  • Grant the minimum permissions needed for the group.
  • Review share access when project membership changes.
  • Avoid giving delete permission unless the team workflow requires it.