User creation and management

Users can be added, modified, and deleted through SafeCom Administrator.

Creating and managing users are described in the following sections.

User-related data is sorted according to the following categories.

 Personal data

Personal data includes the user’s full name (John Smith), user logon (JS), domain and e-mail ([email protected]). This data can normally be imported.

The user logon is a mandatory maximum of twenty (20) characters and must be unique within a domain. User logon is normally the same as the user’s Windows logon.

 Authentication data

Authentication data includes the card number and an optional 4-digit PIN code. If cards are already used for existing purposes, such as building access, then it may be possible to import data from an existing database.

The card number is mandatory, case sensitive, maximum thirty-nine (39) characters and must be unique.

 Settings data

Settings data is specific to the SafeCom solution, so it is not possible to extract and import this kind of data from other systems. However, to make administration easier, define a default user and let new users inherit settings data from the default user (7.2).

3.4.1 Import user data from other systems

To make administration easier, data can be imported from other systems including those solutions with a large number of users.

SafeCom Administrator includes a user import wizard that can import personal data via Windows Active Directory (AD) and Novell eDirectory (NDS eDirectory v.8.7.3 or later). It is also possible to import both personal and authentication data via XML and CSV (7.3).

SafeCom Administrator API (option) is an XML-based tool that makes it possible to manipulate multiple users, automate tasks and integrate your SafeCom solution with other systems.

3 Planning your SafeCom solution

3.4.2 Create users at first print

The SafeCom solution is capable of creating users automatically the first time they print via the SafeCom solution. This method keeps administrative

overhead to a minimum.

How it works:

1. The user clicks Print in Windows and selects a SafeCom Pull Printer.

2. The document is transferred to the SafeCom server. The server extracts the user logon and finds that the user is unknown and/or a card (or ID code) needs to be registered with the user.

3. If the user is unknown the server creates the user based on the default user properties. Next it sends an e-mail to the user, explaining how to collect the document. See the e-mail template example in section 7.19.

Prerequisites:

 The user logon (JS) and the e-mail domain (safecom.eu) can be combined to create a valid user e-mail address ([email protected]).

 The user must enter the e-mailed 8-digit PUK code to register their card or ID code.

For step-by-step instructions see 7.4.

3.4.3 Let users register their card themselves

If your SafeCom solution allows users to enter a PUK code at the device, users can register their cards themselves.

How it works:

1. Start SafeCom Administrator and then locate or add the user.

2. Provide the user with the 8-digit PUK code or let the system e-mail the PUK code to the user (5.7.4).

3. The user goes to the device and uses the card. The SafeCom solution finds that the card is not yet registered to a user. The user is asked to enter the PUK code once (and a personal PIN code twice).

4. If the PUK code is wrong the registration fails and the user is asked to enter the PUK code again.

The user can click Exit to terminate the process.

5. The card is registered with the user when the screen displays:

Operation succeeded. Please login again.

Prerequisites:

 Users must be able to enter their PUK code at the device, for example by having at least one MFP with SafeCom Go or a printer equipped with a

3 Planning your SafeCom solution

3.4.4 Let users register an ID code themselves

If your SafeCom solution allows users to enter a PUK code at the device, users can register an ID code themselves. The ID code is case sensitive.

Note: Normally the administrator handles the registration of user and ID code.

See to 3.4.6.

How it works:

1. Start SafeCom Administrator and then locate or add the user.

2. Provide the user with the 8-digit PUK code or let the system e-mail the PUK code to the user (5.7.4).

3. The user goes to the device to log in. The user enters a unique ID code.

The SafeCom solution finds that -the ID code is not yet registered with a user. The user is asked to enter the PUK code once (and a personal PIN code twice).

4. If the PUK code is wrong the registration fails and the user is asked to enter the PUK code again. The user can terminate the process.

5. The ID code is registered with the user when the screen displays:

Operation succeeded. Please login again.

Prerequisites:

 All devices must allow users to enter PUK codes and ID codes.

3.4.5 Let administrator register cards to users

How it works:

1. Start SafeCom Administrator and then locate or add the user.

2. Open the ID code tab in the User properties dialog (5.8.3).

3. Click Listen and use the card with the connected card reader.

4. If no PIN code is entered the user is assigned the default PIN code ‘1234’.

Prerequisites:

 The computer must have a card reader installed (4.18).

 Users must turn up in person to have their card read and a person with administrator rights must be present to operate the computer.

 Administrator must inform the user of their PIN code.

3 Planning your SafeCom solution

3.4.6 Let administrator register ID code with users

How it works:

1. Start SafeCom Administrator and then locate, or add the user.

2. Open the ID code tab in the User properties dialog (5.8.3).

3. Enter the ID code (case sensitive).

4. If no PIN code is entered the user is assigned the default PIN code ‘1234’.

The user may change the PIN code subsequently (3.4.7).

Prerequisites:

 Administrator must provide users with an ID code and PIN code.

3.4.7 Allow users to change their PIN code

If Allow users to change PIN code is checked on the Users tab in the Server properties dialog (5.7.2), then users can change their PIN code using any of the below methods:

 Using the SafeCom G3 Web Interface.

 On devices equipped with SafeCom Color Front-end.

3 Planning your SafeCom solution

3.4.8 Determine user’s home server

If SafeCom Multiserver Support is enabled the home server denotes the

SafeCom server where the user’s print jobs remains. If the server group consists of only one SafeCom server there is no need to specify home server, since it is identical to that one SafeCom server.

The user’s home server can be specified in SafeCom Administrator. Refer to 5.8.1. If the user changes home server documents will not follow, but will be deleted according to the specified time jobs are allowed to remain on that SafeCom server.

If no home server is specified the user’s home server will become the one that is first contacted. First-time contact is when the user prints to a SafeCom device or logs in at a SafeCom device.

Users that are created at first print (3.4.2) will by default get the master server as home server.