In the following we are going to explain the user interface of Q.wiki.
1. Q.wiki content:
In this frame you will find all contents of Q.wiki. Through the Process map you can navigate through the content and find what you need.
2. Q.wiki logo:
The logo can be individually customised by your company. Therefore you can check the insturction of change logo. Also with a click on the logo you can always get back to the process map.
3. Search:
When you are searching for a specific topic you also have the option to search for content. For that you can also check the instruction search content.
4. Notification, Tools and personal profile:
Notification: If a colleague started a change proposal or you should submit a read confirmation you will find the notificatiosn here. Next to that you also get a mail with the most important information what happened in your Q.wiki. That can be adjust in the personal profile (more to that below)
Tools: The tools are localised by module. There are three subdivisions:
1. the tool button at the top right: for general tools that are only visible to key users
2. the 3-dot menu on the left-hand sidebar: There are the tools for all users, to which everyone has access.
3. gear wheel in the left sidebar: another special function for key users to make settings for the respective module
For more specific information please check the instruction Tools
Personal Profile:
- My page: Favourites, tasks and pages waiting for approval are displayed
- My profile:
- Personal information: Name, e-mail address, login name or the password can be changed
- Roles: Access to personal role overview (details on the role feature in the Q.wiki)
- Notifications: Configuration of notification frequency (email summary daily or immediately selectable)
- HelpCenter: if questions arise while working with Q.wiki, the HelpCenter can be called up quickly
- Release Notes: here you can go directly to our Product Portal. Both the current and the old release notes can be called up here to familiarise yourself with the relevant changes in Q.wiki. You can also submit ideas/suggestions for improvement directly to our product management.
- Log out
5. Edit, Create Child page, set favourite
Edit:
- Process map can be changed: for that check edit Process map
- Through the image-map you can link pages so that the process map becomes clickabel: for that check: making images cklickable.
6. References, History, Manage:
References
History: past changes can be viewed here, or statuses can be compared with each other
Manage:
- page preferences
- move page
- change context
- delete page
- print page
- edit wiki text
7. Welcome Message
You can use the broadcast message to leave a welcome message and provide information about the current structure of Q.wiki. For that check: Show broadcast message on Start page
8. movable navigation bar
The navigation bar can now be detached at the top. This allows the navigation list to collapse and expand dynamically and generates even more space for the valuable content in the management system
9. Navigation bar
Processes, standard assignments and the glossary are activated by default in Q.wiki and can be used. If further modules or knowledge modules have been added, these are also displayed (e.g. audits, risks, news, etc.). The glossary, roles, user profiles and standards assignment modules have now been neatly integrated into the overarching modules and are no longer displayed separately.
10. Help while using Q.wiki
If you have any questions about using Q.wiki, you have two options for getting help.
- Q.wikinger: Q.wikinger provides interactive training via Q.wiki and can be used to train employees. Important information (such as new releases) is also announced via the Q.wikinger. Individual tours can be found using the search function.
- Help Centre: The help button provides answers to questions about the Q.wiki. You can either search for Help Centre articles or send a request to the support team.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article