Directory and HRIS import

Proxon uses your directory to attach AI usage to real people, teams, and reporting lines. Today you bring that directory in with a CSV file. Direct connections to HRIS systems are coming, and will keep the same information up to date on their own.

The file format

Each row is one person. The only required column is email, which is the unique key that identifies each person. Every other column is optional, so fill in the ones that are useful to you and leave out the rest.

Column	Required	Description	Example	Rules
email	Required	Work email, used as the unique key for each person.	jane@acme.com	Must be unique.
name	Optional	Full name. Use this, or first_name and last_name together.	Jane Doe	Up to 255 characters, trimmed if longer.
first_name	Optional	Given name, paired with last_name.	Jane	Up to 255 characters, trimmed if longer.
last_name	Optional	Family name.	Doe	Up to 255 characters, trimmed if longer.
job_title	Optional	Role or title.	Staff Engineer	Up to 255 characters, trimmed if longer.
department	Optional	Primary org unit.	Engineering	Up to 255 characters per name. A longer name rejects the import.
team	Optional	Sub-group within the department. Separate several with a semicolon.	Platform;Hiring	Up to 255 characters per name. A longer name rejects the import.
groups	Optional	Advanced. Department and team paths, used instead of the department and team columns. Nest with a slash, and name the manager with an angle bracket and their email.	Engineering/Platform>alice@acme.com	Up to 255 characters per name. A longer name rejects the import.
manager_email	Optional	The manager's email, which links the reporting line.	alice@acme.com	Must match another person's email.
manager_id	Optional	The manager's employee ID, used instead of manager_email.	E-1001	Up to 255 characters. A longer value rejects the import.
id	Optional	The employee ID from your HRIS.	E-1042	Up to 255 characters. A longer value rejects the import.

Describing teams and reporting lines

You can place someone in the organization in one of two ways, and you should pick one or the other for a given person rather than mixing them.

The simple way is to fill in the department and team columns, and to name the person's manager with manager_email or manager_id. The advanced way is to use the groups column, which lets you write nested paths with a slash and name the manager inline. Use the groups column when your structure is deeper than a single department and team.

Uploading the file

You upload the CSV from your organization settings in Proxon. If a required value is missing, an email is not unique, a manager email does not match anyone, or a name is too long, Proxon rejects the import so you can fix the file and upload it again.