SYNC: People
When importing data to Silverbucket it is vital to keep the structure identical to the example datasheet to ensure a flawless import:
- First row contains the names of the headers - it is not necessary to edit the first row.
- Second row in your file is where your data starts to get imported
- Columns need to be in the same exact order as in the examples
- Rows after the default structure's last column are never read / handled when importing
- Never have hidden columns in your data sheets
What data is this integration used for
- People with simple metadata
You can use this integration to import all your personnel to Silverbucket. Results can be found in People > Listing, for example.
Integration's data fields
Person's first name
Person's last name
Person's e-mail
Default role to be added for the person
The example file in the screenshot will integrate / create the following:
1) A person called 'Support User123' with the email 'supportuser@email.com' with a default role called '1st line support'.
2) A person called 'Supervisor Boss' with the email 'boss@email.com'. This person will receive the system's universal default role ('Project member' by default)
3) A person called 'newuser' with the email 'newuser@email.com'. This person's first name, last name are left blank. This person will receive the system's universal default role ('Project member' by default)
4) A person called 'John Johnson' with no email information. This person will receive the system's universal default role ('Project member' by default)
Rules & basic principles of this integration
Silverbucket matches rows to Silverbucket's data case-sensitively ("SilverBucket_Support" is not considered the same as "silverbucket_support").
However, matching email fields is done case-insensitively (" Support@Silverbucket.Com " is considered the same as " support@silverbucket.com " when creating a user, for example)
- Username is generated from email if it's given. For example " foo.bar@silverbucket.com " -> username will be " foo.bar "
- If email is missing, username will be created from first name + last name. For example "Foo Bar" -> username will be " foo.bar "
- If first name is missing the integration uses last name
- If last name is missing the integration uses first name
- If none of these are given random series of numbers are generated
- Default role will be set to default role if it's not given on the integration data. You can check your default role from the admin panel's Roles tab
- New roles are created if role with the given name is not found from Silverbucket.
- New users are added with default values of the environment. Defaults:
Currency = EUR
Start date = Today (date if importing)
UI Language = English
- Users' information that are already found in Silverbucket will be updated
-> email is used to identify and match user accounts
If the data structure was correct, you can see the outcome in Silverbucket right after the upload. You can make sure the personnel were added by searching for them in Silverbucket or by using the People > Listing -view, for example:
people_import.csv
42Bytes, Uploaded 7 months ago
people_import_exampleRow.csv
108Bytes, Uploaded 7 months ago