Resource Management

Introduction

The Resources module is the repository of identities and rights. Beyond simple users, Process Studio uses several key concepts to manage processes and security.

It is fundamental to clearly distinguish these notions:

Concept	Technical Definition	Main Usage	Example
User	Nominative account (Person)	Login, Signature, Tasks	John Doe
Service	Hierarchical node	Structure, N+1 Validation	IT, Accounting
Role	Static group	Permanent business function	Accountants, Auditors
Actor	Algorithm (C# Script)	Dynamic recipient resolution	The requester's manager
Profile	Set of UI rights	Display of menus and views	Standard User

Interface and Ribbon

Management is done via the upper ribbon:

• Creation Group: To declare new entities (Service, Actor, Role, Profile).
• Actions Group: To delete or manage assignments (e.g.: add a user to a role).

1. Roles (Static Assignment)

A Role is a functional label. It's a simple container in which the administrator places users.

• Nature: Static. The list of members only changes if an administrator modifies it.
• Usage:
  • Generic task assignment: "Send to mail service".
  • View security: "Only Management can see this report".
• Creation: New role button.

2. Actors (Dynamic Assignment)

An Actor is a calculation rule. Unlike a role, it doesn't contain a list of people, but a logic to find them at the right moment.

• Nature: Dynamic (C# Script or Assembly).
• Definition: An actor executes a script that takes the case context (the document, the initiator) and returns a list of users.
• Usage:
  • Workflow: "Send to the initiator's N+1 Manager" (The recipient changes depending on who starts the case).
  • Business: "Send to the project manager indicated in the form".

[!TIP] Developers: An actor is defined by a C# class implementing an Execute method that returns an ICollection<string> (logins or emails).

3. Profiles (Display Rights) and Groups

• Profiles: They determine what the user sees on their portal (Left menus, Dashboards). A user without a profile will see an empty portal.
  • Example: The "Manager" profile gives access to the "Validation" menu.
• Groups: (Less frequent) Used for technical needs or to group permissions.

4. Services (Hierarchy)

Services structure the company. They carry two crucial pieces of information for workflows:

1. The Manager: The service manager (used for hierarchical validation).
2. Membership: Who works in this service.

(See Organization for detailed service management).

5. User Management

The user record is the central element that connects all these notions (Service membership, role possession, profile application).

See the dedicated article: Detailed User Record to learn everything about account creation, security, and connection.

Related articles

• Organization
• Forms
• Process Studio