The user role serves as the foundation for other, more specific roles and is typically set as the default role within the platform. It encompasses the set of permissions that most people working with the platform have.

Assign the role to

The user role serves as the basic level of permissions that every platform user possesses. It is assigned to users who don't have significant responsibilities on the platform.

Users with the user role can edit existing pages but are not permitted to create new ones. They can utilize all the social features and interact within the platform, but they don't have the authority to make global changes to the platform's structure. No administrative permissions are granted to users with this role.

Create the role

A typical user role has the below permissions. You can see the definitions for each permission in List of permissions.

General

• "Access and add likes/reactions": As Haiilo offers a social intranet platform, users should be able to like or react to the content they like.
• "Write comments": Comments open the feedback channel for users across the organization, and just as likes, they are a key ingredient to bringing the social component into the intranet.  
• "Delete comments": If users can create comments, they should also have the option to delete their comments if, for example, a typo occurs. Of course, this permission only applies to comments a user has written themselves.
• "Access file library": Allow users to access their personal file library via the "My files" button within the drop-down menu in the right corner of the horizontal navigation.
• "Manage and delete files in documents": Allow your users to add documents to the platform. Of course, you can later limit their ability to add files for each document library individually.
• "Access colleague list": This permission defines if users can access the list of colleagues, an elementary feature of a social intranet.
• "Search": Without this permission, users can't use the platform search anymore.
• "Access homepages": Without this permission, users can't access homepages anymore and would see a blank page instead.
• "Report content": Every user should be able to report inappropriate content if they encounter it.
• "Use hashtags": This permission allows users to use, manage, and subscribe to hashtags. Before providing this permission to your users or any other role across the platform, please decide if you want to use hashtags in general. 
• "Access Analytics": This permission allows users to access the analytics section of a page or community they are an admin of. 

Pages

• "Access pages": Users need this permission to access pages and the overview of pages. Of course, every user can only access pages that are either public or they have access to.
• "Edit page": Allow users to enter and manage the settings of a page they are assigned as an admin. If a user is not an admin of any page, this user can't utilize this permission.
• "Manage apps of a page": Allow users to add, manage, and delete apps on pages that they are assigned an admin of. It's important to note that this permission can only be utilized if a user is an admin of a page and only for the pages the user is an admin of.
• "Follow page": It is crucial to allow users to subscribe to pages to actively personalize the platform and orchestrate the personal timeline on the homepage.

Although it might seem scary to provide all users with the permissions "Edit page" and "Manage apps of a page", it is strongly recommended to do so to create an efficient roles and permissions concept. Both permissions only apply to pages that the specific user is an admin of. Also, this means you can assign a user the responsibility to manage and maintain a page without the need to change their role to "Editor", which would come with several further permissions on top.

Communities

• "Access communities": To drive platform engagement and cross-departmental exchange, enabling communities for your platform is recommended. This permission allows the users to access the overview of communities and communities that are either public or the user got invited to.
• "Create community": As communities focus on topic-related exchange and a very democratic character, it is recommended to handle them and their creation process as transparent and flatly as possible. This permission allows users to create a new community. 
• "Edit community": Allow users to enter and manage the settings of a community they are an admin of. If a user is not an admin of any community, this user can't utilize this permission.
• "Manage apps of a community": Allow users to add, manage, and delete apps in communities they are an admin of. Important: This permission can only be utilized if a user is an admin of a community.
• "Delete community": Allow users to delete a community they are an admin of.

Events

• "Access events": Allow users to access events via the button within the top navigation and through the events app. They can also respond to events they have access to.
• "Create event": Allow users to create their events.
• "Edit events": Allow users to edit events for which they are an admin.

Launchpad

• "Access launchpad": Allow users to access and use the launchpad via the button within the top navigation. This is also a prerequisite for the launchpad links widget, which is commonly used on the homepage.
• "Manage personal links in the launchpad": This permission allows your users to add their private links to the launchpad.

User

• "Manage user profile": Allow users to change their profile and cover image and fill their profile's Information section with their personal information. Profile fields filled from a user directory are locked and can't be adjusted by the user.
• "Manage notification settings": Allow users to decide which channels they want to receive their platform notifications. The users can choose between the channels you decide to provide them with.
• "Manage account settings": Allow users to change their personal settings, including the platform language or timezone.
• "Access notifications": Users can't access the notification bell without this permission. 
• "Access own profile": Allow users to access their profile. 
• Access other profiles": Allow users to access other users' personal profiles.
• "Follow user": It is strongly recommended that you allow your users to follow their colleagues to promote exchange and a connected workforce. Posts by a user that you follow are displayed on the homepage's personal timeline.

Timeline

• "Access timeline on homepage": Without this permission, users can't access the personal timeline on the homepage (even though you might have installed one). As the timeline is the heart of personalization and the primary source of personalized information, it is strongly recommended that permission be granted to every user of the platform.
• "Create timeline items": Allow users to create timeline posts independently. This is a core element of a social intranet.
• "Delete timeline items": Allow users to delete their timeline posts in case an error occurs. Of course, this permission only applies to a user's own timeline posts.
• "Share content": Allow users to share content with pages, communities,, or colleagues. That way, users can direct others to content that might be helpful to them.

Messaging

• "Write and receive messages": Whether you permit your users to use the chat depends on your organization's tool landscape and if you want to use the chat. 

Integrations

• "Edit files with Microsft Office": Allow users to change Microsoft Office documents stored in the platform. Users don't need to download, change, and upload documents anymore; they can directly change the document via the desktop application of the respective MS Office tool. MS Office 2013 or newer is required.
• "Activate Microsoft 365": Allow users to use the features of the Microsoft 365 integration. The M365 add-on is required.
• "Send messages via Microsoft Teams": Allow users to approach their colleagues via Microsoft Teams directly from the colleague's personal profile. The Microsoft 365 add-on is required.
• "Activate Google Workspace": Allow users to use the features of the Google integration. The Google Workspace add-on is required.

Mobile App

• "Enable timeline module": Allow users to access the mobile app's timeline tab, which displays timeline posts from sources a user is subscribed to.
• "Enable news module": Allow users to see the Recent content section of the home dashboard in the mobile app that displays the latest blog articles from a user's subscribed pages.