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.
You can specify the scope of the share contacts.
|Share contact to||Disclosure scope of shared contacts.|
Discloses shared contacts to the organization.
With [All contacts], every member can access shared contacts of teams the member doesn't belong to.
Discloses shared contacts within a team.
Users cannot access shared contacts of teams they don't belong to.
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.
Example: If you create a team as "SkyDesk Corp.," > "Personnel Dept" > "Sales Dept 1", need to create three teams as the below.
step1: create the first hierarchy team "SkyDesk Corp.".
step2: create the second hierarchy team "Personnel Dept" in the lower hierarchy of team "SkyDesk Corp.".
step3: create the third hierarchy team "Personnel Dept" in the lower hierarchy of team "Personal Dept".
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].
- Not enter anything in "uneditable ID" item.
- If you create a third hierarchy team, need to define a team name until the first hierarchy.
Example of the following team composition
- Not modify "uneditable ID" item.
- If you open the file gotten with [Export team list] in Excel format,
[Uneditable ID] be displayed like "1.23+E14". Use it without editing.
- To change the name of a team without changing member assignment, use the file with the changed name without changing the ID.
- You can change the team name, team ID, description, the hierarchy of the existing team.
- The existing team whose ID is not specified in the import CSV is to be deleted, and the assignment to the team is dismissed.
- If you delete a team in the upper hierarchy, you need to delete it, including the lower hierarchical team of it.
- Even when ID 0 is not specified, the organization team is not deleted.
Example of the delete the third hierarchy team "SkyDeskCorp. Personnel Dept Sales Dept 1".
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. email@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|
* 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].