- People
-
Projects
- Projects > Listing & Projects > Allocations
- Project's Dashboard
- Project's Basic Information
- Project Numbers table
- Projects > Allocations Main Graph
- Progress Numbers
- Actions (Project's Dashboard)
- Membership Actions (Project's Dashboard)
- Project's Resourcing View
- Grouping in Project's Dashboard
-
+ 13...
-
Resourcing
- Resourcing with 'Quick Edit'
- Resourcing with 'Grid View'
- Finding and Resourcing the Available & Suitable People for Your Projects
- Soft Booking
- Use Cases for Soft Booking
- Resourcing Log
- Allocation Notes
- Resourcing Requests
- In-Depth: Getting an Overview / Utilization Rate of a Specific Target
- In-Depth: Using the Utilization Range in Person Filters
-
+ 2...
- Reports
- Timesheet
- Competencies
- Resourcing Intelligence
-
SYNC View (admins of Silverbucket)
- Integrating Data with with Silverbucket's SYNC-view
- SYNC-View: Competency
- SYNC-View: Customers
- SYNC-View: Extended-customers
- SYNC-View: People
- SYNC-View: Extended-people
- SYNC-View: Projects
- SYNC-View: Extended-projects
- SYNC-View: Hour-integration (actual hours)
- SYNC-View: OrganizationNodes-integration
SYNC-View: 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
- 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
col. A |
B |
C |
D |
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)
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)
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:

How did we do with this article?