When adding users, it is necessary to set what permissions will be given to each user.
Here we will show some fundamental considerations for giving permissions.
Permission name | Contents | Risk | Who this is generally assigned to |
User type (Regular User) |
Basic operations except for administrator functions |
All users who do not do administrator tasks | |
User type (System Administrator) * When there are important notifications regarding Sansan, the system administrator may be contacted by us. |
Adding, changing, and deleting departments
|
As users can be added, costs will be increased. By deleting users, there is the risk of losing data. |
Person in charge of information systems Person in charge of site Person in charge of customer data management Project manager |
User type (Sectional Administrator) |
Adding, changing, and deleting departments |
As users can be added, costs will be increased. By deleting users, there is the risk of losing data. |
Person in charge of information systems Person in charge of site Person in charge of customer data management Project manager |
All Data Update |
Editing and deleting business card data and reports held by other users |
As all data can be edited or deleted, there is the risk of information becoming incorrect. |
System administrator Person in charge of updating all business cards for maintenance purposes Project manager |
Download Card and Reports (My Data, All Data, Custom, Prohibited) |
Outputting CSVs of business cards and Report data
|
As business cards and Report data are being output as a CSV file, it is necessary to take appropriate precautions for handling it. |
When it is necessary to make address lists for greeting cards, permissions can be given temporarily Project manager |
Bulk Email Function * Only if Email Functions are being used. |
Bulk Email delivery |
As Bulk Emails can be sent to all email addresses inside the viewable business card data, the risk of sending a mistaken email is higher.
|
Project manager Person in charge of sales Marketing specialist Person in charge of email delivery |
Opportunities (User) *Only if Opportunites are being used |
Registering, editing, and viewing Opportunity |
All users using Opportunity | |
Opportunities (Administrator) *Only if Opportunites are being used |
Registering, editing, and viewing Opportunity Master |
As Opportunities data for each existing master can be edited or deleted, there is the risk that by an operation mistake data could be deleted.
|
Project manager Person in charge of information systems |
API * Only if API functions are being used |
Connecting with external systems through APIs |
As Sansan business card data will be integrated with external systems, it is necessary that appropriate precautions be taken.
|
Person in charge of information systems Project manager |
View Usage Record |
Downloading information about user log in frequency, Reports, Opportunities, number of business cards registered, and date of most recent log-in.
|
Project manager Project leader Other people advocating Sansan usage |
|
API Connection |
Connection with external systems by using Zapier
|
As Sansan business card data will be integrated with external systems, it is necessary that appropriate precautions be taken. | Person in charge of information systems Project Manager |