System administrators can add Sansan users and change the user information and permissions. Here we will explain the different items that can be set for Sansan users.
Item names and explanations
|Account lock||Only displayed when a user has been locked out of his or her account. By clicking on "Reset password", a password email will be sent to the email address of the relevant user. For more details, see here.|
|Department||Here you can select which department a user belongs to. Users can be set to belong to multilpe departments; this will be displayed with a comma between the departments. For how to create or edit departments, see here.
|User ID||The ID used to identify a user. Multiple users cannot have the same user ID. Also, once a user ID is registered, it cannot be changed.|
|Name||The name that will be dispayed as the owner or person registering data. The same name cannot be used by multiple users.|
|Email address||The email address used for logging in. This is necessary for receiving news from Sansan and for confirming identity when reissuing passwords.|
|Sub-Email address||Users can receive news emails and reminder notifications from Sansan. By setting this to a mobile email address or to the address of an assistant, it can be very useful. This however cannot be used for logging in.|
|Start Using Date||The date that the user started using Sansan.|
|Language||The Sansan display language (Japanese, English, and Chinese (simplified characters))|
|Format for Incoming Email||The format that emails will be automatically sent in can be set for each user here to either HTML mail or text mail.|
|AD Integration ID||The ID necessary for doing AD linking. This is not the user ID of the AD.|
|User Type||The permission level of users can be set. System administrators can do administrator settings such as adding users and granting permissions; department administrators can do the same operations as system administrators, but only for the departments allowed. (However, some permissions of department administrators are restricted). Also, when there are important notifications regarding Sansan, our company may contact the system administrator. For things to consider when granting permissions and the risks involved, please see here.|
|All Data Edit||Users can edit and delete business card data held by other users.
(Usually, users can only edit or delete business cards they have).
|Download Cards,Reports (My data)||Users can download business card or contact information they have.
For more details about donwloading bsiness cards, see here. For more details about downloading contacts, see here.
|Download Cards,Reports (All data)||Viewable business card and contact information can be downloaded.|
|Email Function||Users can use bulk email delivery to send emails to all viewable business cards.|
|Salesforce Integration||Users can use functions to link with Salesforce. For information about how to set this up or which versions it applies to, see here.|
|Opportunities (General User)||Users can register and view deals. For more details about deal functions, please see here.|
|Opportunities (Administrator)||Users can create deal masters and items, and set email notifications. For more details, see here.|
|API Connection||Users can issue an API key. For programs that use APIs, it is necessary to have an API key. API keys are necessary for each individual user. As Zapier linking uses the same shared API key, they can be used with the same permission.
For a more detailed explanation of API linking, please see here.
For a more detailed explanation of Zapier linking, please see here.
|View Usage Record||Users can download usage reports of users. For more details about each item, see here.|
|Download organization tree||Users can download the Organization tree. For more details about each item, see here.|
* Number / Number of contract IDs
The number here will be the number of allowed users in the contract. Users who are on a different contract in the same company are not included.