Team Management CSV Upload
- Jeremy Freeman
Allstacks provides a mechanism for managing rosters and tags through a CSV sync. You can either provide the csv roster to your CSM or you can join our alpha for the CSV upload API. Both methods are designed to allow you to export a roster and user properties from an internal system, like your HRIS, and manually sync your employees details and teams to your Allstacks configuration.
Method 1: Provide a roster CSV to your CSM
You will need to construct a CSV file that looks similar to the following:
Note that the CSV will be required to have the following elements:
A Header row, where the first header is always “User Work Email Address”, and the following headers are the categories of tags to create.
Categories are types of attributes, like the following: “Geography“, “Function“, “Role“, “Department“
One row per employee, where the first cell is the users work email address used for the connected SDLC tools. The remaining columns are the tags to add to the user within the category. If an employee needs more than one attribute in a category, you can duplicate columns to add multiple. Blank cells are ignored
Once you’ve created this CSV dump, your CSM can enable and create all of your tags and enable your users on your behalf.
[Alpha Access Required] Method 2: Upload the roster to an endpoint
Once access is enabled for your account, you will be able to upload the exported CSV to the following endpoint. This method is for teams that have frequently changing rosters and attributes, or that want to manually sync this data themselves.
Endpoint
app.allstacks.com/api/v1/organization/{your_org_id}/service_user_tag_hierarchy/upload_employee_tags
Parameters:
Org_id: This is the unique identifier of your organization, and can be found in the URL of the contributor management page.
File: This is the CSV report described above to be uploaded. Format and structure of this file can be found in the following Postman file
Reconcile_tags: If True, users present in the file will have all tags cleared before new tags are created, resulting in your Allstacks configuration matching the file exactly. If False, this process will only create new tags, and will not destroy any existing ones.
Return Status:
200 if the file was successfully submitted. This request does not actually upload the tags, the 200 only confirms that a job was kicked off in AWS with the file submitted. The job itself is what uploads the tags, and once it’s finished you’ll receive an email.
This job usually takes around 5-15 minutes while the job is uploading tags. You’ll see the tags slowly import into Allstacks during this team.
Postman Example:
You can also leverage the following Postman example to try it out yourself.
