Falcon enables you to establish a very differentiated permissions structure for your projects. In this article we will briefly explain how this works and what the effects are for the individual users.

Note: This article does not refer to the permissions of admin users or hub owners.

Guarded vs. Public

The first level of permissions restriction is whether an element is guarded or not:

If an element is public, users can make the following adjustments:

Profile-Tab at all levels

  • edit Name and Description
  • change Responsible, Budgeting Item & Phase

Schedule-Tab at measure level

  • Create new activities
  • Change activite name of unfinished activities
  • Change actual / forecast date of unfinished activities
  • Change responsible for unfinished activities 
  • Delete self created activities
  • Change comments of unfinished activities
  • Set unfinished activites to done

Note: A user without admin permission can neither change the plan date nor edit already checked activities afterwards.

Effects-Tab at measure level

  • Edit actual / forecast column


  • Look at other status reports (at all levels)
  • Create status reports (only at measurelevel)
  • Edit and delete own unchecked status reports (at all levels)

Write vs. Read

If an element is guarded and a user has no permissions or responsibilities for or in this element, it is not visible to this user. 

Note: If a user is responsible for an element, he automatically receives write permission. A write permission on the upper level is inherited on the lower levels. The responsibility for an activity leads to a write permission for the associated measure.

The user permissions can be edited in a more differentiated way by distributing a write or a read permission or assigning an invisible permission in order to counteract inheritance.


If, for example, a user receives write permission for a guarded measure, he has all the permissions he would have in an public measure (see above). 


The reading permission, on the other hand, ensures that the user can view a guarded element, but cannot make any adjustments to it.


The admin permission ensures that a user receives admin permission in a certain project. So he can insert new elements and also work in the plan column.

Note: The admin permission can only be assigned at project level (highest level).

Did this answer your question?