Which initiative roles and other user types exist?

Most of the time, the person who starts an initiative, also manages and promotes it. However, in some cases, these different roles within one initiative are divided between multiple people.

To support this, the platform uses these different roles to manage these tasks and responsibilities. Front- and backoffice permissions, workflows and automated emails are linked to these roles. 

Most of these roles are assigned automatically and can be adjusted from the backoffice. 

    Initiative roles

    We have 5 different roles on the initiative level.

    An Initiator is a member that has initiated and created an initiative. An initiator is displayed on the initiative level and can: 

    • Create initiative and activities. 
    • Edit his own initiatives and activities (Draft & Running).
    • Post updates to his own initiative, on the activity walls and share these by email.

    By default, the Activity Manager coincides with the Initiator. This role manages all activities and receives emails linked to these activities. An activity manager is displayed on the activity level, unless an activity owner is listed. They can: 

    • Create and edit activities.
    • View profile, motivation and CV of activity applicants.
    • Accept or reject activity applicants.
    • Post updates to the initiative and activity walls and share these updates by email.
    • Review activities, and confirm applicants. Learn here how this works.

    Promoter is an optional member status which appears on the initiative overview. This could be a well-known person or a co-initiator within the organisation. They can be added to an initiative by the platform manager.

     A promoter is displayed on the initiative level and can: 

    • Post updates to the initiative and activity walls and share these by email.

    A Partner organisation shows whenever there is a Partner organisation (contact) listed when the initiative is created. The organisation's contact person can be found in the backoffice. 

    • The Initiator partners with this organisation.
    • If the partner needs an active role, they can (get a) login.

    A Reviewer is an optional member status which is only displayed in the backoffice. This role is mainly used in platforms with multiple back-office users who have to review initiatives.

    Activity roles 

    By default, An Activity owner is the same member as the initiator and the activity manager. This member manages the activity and receives the emails linked to this activity. If different activities need to be managed by different members, an activity owner could be assigned in the backoffice. An activity owner displays on the activity level, and can: 

    • View profile, motivation and CV of activity applicants
    • Accept or reject activity applicants
    • Post updates to the initiative and activity walls and share these by email
    Review activities, and confirm task and event members. Learn how.


    A contributor is the overall term to describe anyone who makes a contribution on the platform, either by creating an initiative or starting or joining any type of activity.

    A participant is a user who joined an event activity.

    A supporter made a donation to a crowdfunding campaign activity. 

     


    Other roles  

    A visitor is a person who visits the platform without an account. Closed platforms can't have visitors. A visitor can:


    • share initiatives.
    • comment on initiatives and activities.
    • make donations.
    • become a member.

    A member is a person with a platform account, and can:

    • share initiatives.
    • comment on initiatives and activities.
    • make donations.
    • sign up for activities.
    • create initiatives and activities.

    A Partner is a member with Partner permissions, and: 
    • could be an external member.
    • is visible on the initiative level.


    A Platform Manager is a member who can access the backoffice
    • to enter and use the backoffice.
    • to assist other users with issues and questions.
    • multiple members can have back office "Staff" permissions.
    • using the "URL/admin" to login.