Box

Connection

Connecting sends you to Box to approve Klef’s access.

Permissions

Minimum permissions the connection requires.

Capability	Required	Granted by (any one)
Provision users	Yes	`manage_managed_users`, `Manage users`
Manage groups	Yes	`manage_groups`, `Manage groups`

box.user

Fields

Field	Type	Required	Description
`email`	string	Yes	Email address the user signs in with. Klef does not change it once the user exists.
`name`	string, up to 50	Yes	Full name.
`role`	enum		Role in the enterprise. Defaults to user. Values: `user` (User), `coadmin` (Co-admin).
`jobTitle`	string, up to 100		Job title.
`phone`	string, up to 100		Phone number.
`address`	string, up to 255		Address.
`groups`	grant		Groups the user belongs to. One row grants one group.
`groups[]`	string		Group ID.
`active`	bool		Whether the user can sign in. An inactive user keeps their content, which is how Klef removes one.

Default Account Matching Rules

When Klef adopts an account that already exists in Box, it works out whose it is by trying these in order. A connection can override them.

Account field	Worker field
`email`	`worker.business_email`

Examples

Box users

A Box user for every employee, deactivated with their files kept when they go.

stage active {
  target box.user {
    email    = worker.business_email
    name     = worker.display_name
    jobTitle = worker.job.name
    role     = "user"
    active   = true
  }
}

Basics

Connectors

Administration

Box

Box

Connection

Permissions

box.user

Fields

Default Account Matching Rules

Examples

Box users

​Box

​Connection

​Permissions

​box.user

​Fields

​Default Account Matching Rules

​Examples

​Box users

Box

Connection

Permissions

box.user

Fields

Default Account Matching Rules

Examples

Box users