When a Cards R organization is created, a team of the organization name is created automatically.
This team is the [Organization team].
You can add teams other than the organization team.
The organization team cannot be deleted.
There is no other difference between the organization team and other teams.
At adding a member to the Cards R organization, the organization team is set as default.
Without changing the default settings, all members belong to the organization team.
If you will manage contacts by team-privately, you have to remove members from the organization team in addition to let them join each team.
The user belonging to no team can view the only contacts related to the user.
The user with the privilege in the system settings can add/modify/remove teams and add/remove members to/from a team.
By purchasing paid team options you can increase the number of teams that can be created.
If you cancel the purchase of the team option after creating teams, all created teams will be deleted.
The name and the ID is required to a team.
Teams are shown in the order of ID.
Team ID should be a unique positive number.
Team ID 0 specifies the organization team.
If a user join a team, contacts related to the user are shared to the members of the team.
The [not shared] belonging option enables that the user can access member contacts without disclosing the contacts of the user.
The [not shared] option is available when [Share contact to] is [Within team].
You can create a team up to the third hierarchy.
You cannot delete the team which has the lower hierarchical team. Delete from the bottom team.
When you create a third hierarchy team, need to create a team until the second hierarchy. In this case, team counts is three.
You can specify the scope of the share contacts.
Item | Selection | Description |
---|---|---|
Share contact to | Whole organization | Discloses shared contacts to the organization. With [All contacts], every member can access shared contacts of teams the member doesn't belong to. |
Within team | Discloses shared contacts within a team. Users cannot access shared contacts of teams they don't belong to. | |
The following items are displayed only when [Share contact to] is [Within team]. | ||
Aggregate contact to | Whole organization | When aggregating contacts, we will identify them as shared contacts for the whole organization. |
Within team | When aggregating contacts, they will be aggregated with team contacts. The contacts of teams that do not belong will not be identified. |
You can set the name and the ID of teams in the Cards R organization.
You can get the CSV format of team settings with [Export team list].
Team name | Team ID | Description | |
---|---|---|---|
![]() |
0 | ||
![]() |
100 | Since November 2016 | |
![]() |
101 | Tentative settings. | |
Sales Dept 1 | 1011 | ||
Sales Dept 2 | 1012 | ||
![]() |
102 |
[Uneditable] ID | Team name(hierarchy1) | Team name(hierarchy2) | Team name(hierarchy3) | Team ID | Description |
---|---|---|---|---|---|
tid1234567 | Cards R Org | 0 | |||
Example Corp | 100 | Since November 2016 | |||
Example Corp | Personnel Dept | 101 | Tentative settings. | ||
Example Corp | Personnel Dept | Sales Dept 1 | 1011 | ||
Example Corp | Personnel Dept | Sales Dept 2 | 1012 | ||
Example Corp | Marketing | 102 |
[Uneditable] ID | Team name(hierarchy1) | Team name(hierarchy2) | Team name(hierarchy3) | Team ID | Description |
---|---|---|---|---|---|
tid1234567 | Cards R Org | 0 | |||
tid2345678 | Example Corp | 100 | Since November 2016 | ||
tid3456789 | Example Corp | Personnel Dept | 101 | Tentative settings. | |
tid4567890 | Example Corp | Personnel Dept | Sales Dept 1 | 1011 | |
tid6789012 | Example Corp | Marketing | 102 |
You can set belonging teams and belonging type (shared or not shared) to each member of your Cards R organization by CSV file.
You can get the CSV format of team settings with [Export team member list].
If a user joins to a team normally and joins to the other team as belonging without share, two lines of join normally and join as [NOT SHARED] are required. (e.g. mary@example.com in the example ).
Even when the [not shared] option is not available, i.e. when [Share contacts to] is [Whole organization], the CSV element for the belonging type is required.
The teams a user belongs to are set as the file.
To add a team in addition to the current belonging team, both adding and current teams should be specified.
To remove a member from all teams, specify the email of the member and belonging type without team IDs.
Multiple teams can be specified to a user. [Export team list] provides the list of team IDs.
[Set team member from file] doesn't change teams of the members which are not specified in the file.
Example of team member setting file
Belonging type | Beloging team ID | ||||
---|---|---|---|---|---|
mary@example.com | SHARED | 1 | |||
mary@example.com | NOT SHARED | 3 | 5 | 11 | |
bob@example.com | SHARED | 5 | |||
john@example.com | SHARED | 1 | 3 | ||
beth@example.com | SHARED | 11 |
* A cell means an element of a CSV file.
* You can specify teams successively without blank elements.
We strongly recommend that you preserve the current setting with [Export Team List] and [Export Team Member List] before executing [Set Team from File] and [Set Team Member from File].