All user objects inherit from the abstract UserBase class.

 

Members vs. Users

It is then divided into 2 different types, the member object and the user object. A member object only has access to password protected areas within the web site and the user type that can also access the site admin pages.

The number of user objects (admin users) is tied up to the E-Site licensing model, the member object isn’t (members).

 

Member profile system

A member type user can’t access the admin page feature, but is primarily used with the member profile feature, allowing you to set up an advanced membership system. (Mailing lists, access to password protected areas and site features, forums, payment, etc.)

 

All the member and user objects must be member of one or several groups, their access levels will be added up unless ”Inherit from parent” is not set on the user object (this is default on).

 

Developer user types

Many of the advanced E-Site functions check your user type to grant or deny access to accessing them. An example is the developer functions and server admin functions. Developer menus will appear if your user is one of the three developer user types (or any custom user type inheriting from the ”Developer” class).

 

 

Creating custom user types

Each user object type (or user role) can define the following options:

• Available object types
• Available elements or fields
• Access level to website and admin pages (read / write access)

 

The access levels are configurable on the user objects meaning you can easily define user roles without creating your own custom user types. Creating custom user types is a feature for advanced programmers.

 

For more info please analyze the element structure of the core object types. (Edit object definition for any user)

• the hide_objtypes element hides object types for users of this type (csv list of types to hide)
• the hide_elements element hides elements from object types by name (csv list of fields/pages to hide)

 

Core user types

 

Here is a list of the core user types:

 

Object type name	Description
UserBase	Abstract
Member	Can access the website not the admin pages. Access in configurable on group or overridden on each member object.
User	Can access the website and the admin pages. Group or override on user configuration. This class is abstract.
Admin user	Is the ”normal” CMS user type.
Simplified user	Has only basic CMS access and a lot of advanced settings are hidden and not accessible.
Developer	Abstract class for all developer user types. This is typically the users extending or modifying the functionality in a site. Opening it in Visual Studio, dream weaver, using virtual files, modifying source code or adding custom modules. These are for trusted expert users and programmers.
Site developer	Creating site specific customizations.
Core developer	A user creating his own platform, mass production, making templates, etc.
Server admin	A user with access to the server monitoring functions.

 

 

Changing your user type

This requires developer access (your user object being of a developer user type) or direct access to the application database. Open any user object (also your own) and click the ”Change object type” option on your developer menu. Enter the name of your new desired user type.

If you don’t have developer access but direct DB access open the ”Objects” table and change your ”ObjectTypeID” field into the appropriate type, see the ”ObjTypes” table for a list of the available object types. Reset your app as it caches your user object in memory, meaning it will first change on a reload from the database.