FAQ

An overview of common questions and answers πŸ“š

πŸ–οΈ  How to manage absence approvals?  
A leader under "user roles" has access to "Absence - Manage records and approve requests."

System role/admin has full access to absences. This means that the system role or administrator role has full access to all aspects of absence management, including approval. 

There are instances when leave is automatically approved in Huma, and it only results in a
notification:

1. When a person has the system admin role in Huma or has another system role where 'Absence'
      is enabled.
2. When a user has a 'Leader' role (under user roles) for a team or location. If the leader is also a               part of the same team/location they oversee, the leader's leave is automatically approved.
     This is because the standard 'Leader' role has leave approvals and editing enabled.

If they have a "System Role" with full access to Absence, they will receive notifications from everyone because system roles apply to everyone in the account.

If they have a "User Role" with access to Absence, they will receive absence notifications for those they have this user role over (one or more Teams/Locations, or all in the company).

πŸ“  How to grant access to a completed meeting?
The "meeting host" must grant access, and this is not governed by "system- or user roles".

In meetings, the meeting host can grant other access by adding users to the 'Participants' field. If there is a need to access an already completed/closed meeting, the meeting host can reopen it by selecting the document => clicking on the three dots in the upper right corner => Change status => Opened. Then, one can click on "Edit meeting details" and add more participants to the meeting and "complete" it again so that the minutes are assigned again.


✍️ Can participants write meeting notes?
When creating a meeting, and it is in 'draft' status, participants do not have access to the meeting. As soon as the meeting status is set to 'open', participants have access to the meeting agenda and can suggest their own discussion points. This means that participants do not have the ability to comment on the discussion points/write comments you have already added, but can only add new ones.

So unfortunately no, but maybe it will be a future release. You can leave us a vote for this in our Roadmap here.

πŸ“‘  How to ensure that multiple individuals have access to the document (fx. team)? 
You can do it when uploading a new, or already existing document. Select the document you want to grant access to, and you will get an overview of details. Under 'access,' you can choose to either share the document with individuals or teams/locations. 

If you share access with a location/team, you must be a part of that team/location yourself to be
able to see the documents on the overview page.


πŸ‘©β€πŸ’» Can employees add competence themself? 
No, only users with competency access can register, update, and delete types and competencies.


πŸ“• Is it possible to export the handbook to a Word document or a PDF file?
In Huma, handbooks are designed for digital use and are optimized for both computer screens and mobile devices, including robust search features. Therefore, unfortunately, there is no functionality for exporting to PDF.

The export/import function supports only the .json format, allowing customers to, if necessary, move the same handbook between accounts, for example, in case of multiple accounts due to corporate structure.

πŸ“¨  How do I change the email of an employee?

  1. Access the employee's profile and update the email address listed under the "Intro" section on the profile card. 
  2. After clicking "Save," a pop-up box will appear, where you confirm both the old and new addresses. 
  3. The system will then send an email to the new email address with a link that the user must click to verify the new email address. (If the user has not received the email, ask them to check their spam filter.)
  4. Once the user verifies the new email address, SysAdmin in Huma will receive an email confirming that the user has verified the new email address. 
  5. Only after the user has verified the new email address, the email address field on the user's profile card in Huma will be updated
  6. The user can now log in to Huma using the new email address.

You can configure your dashboard as you want to! Scroll down on the dashboard to' configure dashboard' and choose the order in which you want the topics to appear, and whether they should all be visible.

Did you know that you can navigate through Huma using ⌘ (command) + K on Mac ,  or control + K on PC? ItΒ΄s an easy way to find everything you need in Huma, without clicking your mouse around.