A generic resource allows you to schedule capacity according to a chosen axis (skills, team, external resource).

The generic resource is used when identifying a named resource is impossible or unnecessary.

At the start of a project, for example, when the need for an expert's intervention is known but the name of that expert has not yet been identified.

The resource can be named or generic.

In most cases, a resource is equivalent to a natural person (named resource).

The generic resource allows capacity according to a chosen axis (e.g., a skill, a team, a resource external to the organization).

The generic resource is used when it is impossible or unnecessary to identify a named resource (e.g., at the start of a project, the need for an expert is known but the name of the expert has not yet been identified).

The resource has a genre that allows for differentiation.

Resources can then be sorted, displayed, and filtered according to type. (Examples of resource types: internal/external, billable/non-billable.)

Availability review allows you to display, using a color code, the availability resources according to their assignments and according to a period.

Here are the colors displayed and what they correspond to in detail:

• Invalid availability

• Availability 100%

• Availability 90%

• Availability 80%

• Availability 70%

• Availability 60%

• Availability 50%

• Availability 40%

• Availability 30%

• Availability 20%

• Availability 10%

• Availability 0%

• Availability exceeded

A user will be able to log in to the application, but if they do not have any associated resources, they will not be able to enter their timesheet, be assigned as a resource to projects, etc.

We can say that a user is a connected person, and that a user can have an associated resource.

A resource corresponds to an entity (physical or otherwise) mobilized for a project.

It carries a load, i.e., a number of days required to complete an activity, or remaining work

Most often, the resource is associated with auser(connected person), but this is not mandatory.

You can create a generic resource such as project manager, which will not have an associated user since it may correspond to several people and therefore to several users/resources.