Users

All users must belong to a user group, so if you haven’t created a user group yet, do so now.

The process of creating users can be automated by using the Extranet module – read more about the Extranet module.

Depending on your type of solution, you will have different kinds of users associated with your Dynamicweb system.

For instance, you could have:

• Backend marketing personnel, who use the Dynamicweb Marketing tools to create and execute campaigns
• Backend administrators and editors
• Registered Customers
• Frontend editors
• Etc.

Here’s how to create and configure individual users, and an overview of all the many options you have when working with users – not least how to import and export users, in order to integrate with other systems.

In this section you will learn about:

• Creating (and deleting) a user
• Which user fields are available to you
• How to create additional addresses for a user
• How to access user system information, like orders, loyalty points, saved cards and email marketing statistics
• User types and user-specific settings and configuration options

To create a new user manually:

• Click Users on your accordion, to access User Management
• Right-click the user group you want to add a user to
• Click New user (Figure 3.1)

Figure 3.1 Click 'new user' to start creating a new user

This takes you to the user view, from where you can fill out all the relevant details, permissions, and so forth – before saving (and creating) the user.

At the top of the user view, you will see the user ribbon tabs (Figure 3.2) – read about the different actions you can take from there below.

Figure 3.2 The user ribbon tabs

Below the user ribbon tabs, you will see the user fields –  here’s what you can do with them.

At the most basic level, a user needs only a user name and a password (Figure 4.1).

Figure 4.1 The user info fields are for the most basic information on a user - the user name and password

You can generate a password by clicking the key icon next to the password field, or simply provide one manually.

To use password encryption, check the Encrypt-checkbox. Once saved, an encrypted password cannot be seen, but only reset, from the backend.

I most cases, however, it is useful to have more information about your users than their username.

To make that possible, you have access to a lot of user fields – here’s an overview of all the standard fields available to you in Dynamicweb.

You can enable default password encryption – and customize the encryption options – from the user management advanced configuration settings.

Aside from a user name and a password, the user personal fields (Figure 5.1) are available to you.

This is where you (or the users) provide information about names, titles, addresses, customer numbers, their preferred currency, and so on.

Figure 5.1 User fields for storing personal information about a user

Most of these are self-explanatory, but for those who aren’t, here’s an explanation.

• For the user email field, you can validate the provided email by clicking on the red X or green checkmark icon to the right of the field. The validation process checks both the formatting, and whether or not the domain exists and has a mal server record.
• Speaking of emails, the email permission checkbox is also located here. Be advised, that it is illegal in most countries to send unsolicited (e.g. spam) marketing emails to people.
• You can select a default currency for the user – of the currencies you have created under Ecom > Configuration > Currency, provided that you have eCommerce with Internationalization on your solution. The currency selected will overrule the standard currency settings, but only for this particular user.

In addition to basic and personal information, you can store the work details of a user (Figure 6.1).

Figure 6.1 Fields for storing work-related information about your users

The only field warranting an explanation is the VAT reg number.

A VAT identification number is used in many countries for value added tax purposes – in Denmark, the VAT identification number is called a CVR-number, in Germany an USt-IdNr., in the UK a VAT Reg No – and so forth.

If a user owns a company, or is acting on behalf of one, you can store the VAT identification number here – and access it by using the  Ecom:Order.Customer.VatRegNumber tag in your templates.

With the user GeoLocation fields (Figure 7.1), you can store a geo-location for a user.

Figure 7.1 The geolocation fields

You can use geo-locations to e.g. create maps of your users and user groups, using the maps module.

If you have any custom or system fields on your solution, this is where they appear.

Figure 8.1 User system and custom fields

Read more about creating custom fields here.

In the Groups-field (Figure 9.1), you can see which groups a user belongs to – and add or remove groups to suit your purpose.

Figure 9.1 The groups-field

To add a group, click he folder icon with the green plus sign – to remove a group, click on it, then click the folder icon with the red X.

If your solution uses live prices, you can disable these for a specific user by checking the Disable live prices checkbox (Figure 10.1).

Figure 10.1 Disable live prices by checking this checkbox

At the bottom of a user, you can see audit information (Figure 11.1).

Figure 11.1 The user audit information

You can see when and who created or updated a user – when their email permission settings were updated, and when they last logged in.

Once a user has been created, you can right-click the user and choose between several actions ({fgureref}).

Figure 12.1 Right-click a user to access a number of actions you can take, e.g. deleting or moving the user

You can:

• Edit a user (you can also access the edit view simply clicking on a user)
• Copy a user
• Deactivate a user
• Delete a user
• Add groups to a user, or remove a user from a group
• You can also create a new user from the right-click menu

From the user ribbon bar, you have access to the show buttons (Figure 13.1).

Figure 13.1 The user show buttons allow you to access the addresses and permissions views of a particular user

The user button is active by default, when you’re viewing a user, but you can click the other buttons to see the permissions for the user, or to add additional addresses for a user.

Click the Permissions button to go to the user permissions overview (Figure 14.1).

Figure 14.1 The permissions overview

From here, you can:

• See the frontend and backend permissions for the user. Click on the area marked in red to change between viewing backend and frontend permissions.
• See the module permissions for the user.

This is only an overview of the user permissions – permissions are set in the page, module, etc. itself 

Click the Addresses button to go to the addresses overview.

From here, you can click Add address to add an additional address to the user (Figure 15.1).

Figure 15.1 You can add additional addresses to a user

You or the user can edit and manage these addresses from frontend using the Extranet module Edit profile functionality.

From the User ribbon, you have access to information about the user, and how they interact with your solution (Figure 16.1).

Figure 16.1 The user information buttons

By clicking the appropriate button, you can:

• See details about each visit a user has paid your solution – read about the visitor details view.
• View the order list of the user.
• See which email marketing efforts have been targeting the user, and how they have reacted to them
• See the user’s total loyalty points, and how and when they received them - or add points manually - read about loyalty points.
• See which credit cards (if any) the user has saved on your solution - read about saved cards.
• See a list of previously delivered recurring orders (if any) for the user – read more about recurring orders.

Clicking the Email marketing button will open an overview like in Figure 17.1.

Figure 17.1 See how a user has interacted with your email marketing efforts by opening this overview

With this overview, you can see both a summary of how they have interacted with all your email marketing efforts, and a detailed view of how each email performed.

From the user ribbon, you have access to a number of custom user-specific settings (Figure 18.1).

Figure 18.1 The user-specific custom settings are accessed by clicking the appropriate button in this menu

With these settings, you can:

• Select a custom editor configuration for the user.
• Send the user details to someone
• Allow (or disallow) backend login for the user
• Select a custom start page for the user
• Open the impersonation window for the user – read about impersonation.
• Select an item type to extend the user properties of this user with.

Most of these settings can also be configured on the group level – read more here.

From the user ribbon Options tab (Figure 19.1), you can customize the user type, and you can make the user account expire at a certain point in time.

Figure 19.1 The options ribbon tab

To do so:

• Click the appropriate user type to change the user type
• Specify a time interval between which the user will be valid

By default, a user will never expire – and will be a default user.

Dynamicweb has three user types, representing three different levels of access to the solution.

Default users have no access to critical settings, but can access all areas required for normal maintenance purposes.

The Admin user group has access to semi-critical settings, such as:

• General system and solution settings
• Search index settings
• Editor configuration settings
• Customization of URLs
• Security settings concerning spam and SQL injection etc.
• Access to the Control panel – including advanced module settings
• The ability to install module themes
• The ability to generate image URLs and Navigation XML

The Administrator user group has access to all of the above, and the most critical settings such as:

• The ability to change global settings
• Managing Dynamicweb versions
• Host header setup
• WebDAV settings
• Database configuration

Remember that you can create custom user groups, and control their access by setting permissions on content.

There is no implementer-specific information available for this subject yet.

There is no developer-specific information available for this subject yet.

There is no integrator-specific information available for this subject yet.