How Do You Set Up Users and Roles in Whitevision?
Quick Summary
Whitevision B.V. Declaraties is a Dutch document-processing platform that relies on clearly defined users and roles to determine who can submit documents, who can approve them, and who can manage the system’s underlying settings. Consequently, setting up users and roles correctly from the outset has a direct impact on how smoothly documents move through recognition, approval, and booking, since every document eventually needs to reach the right person. This article reveals how to set up users and roles in Whitevision, covering the core role types, how permissions and approval thresholds are typically structured, and how to manage changes such as new hires, department moves, or temporary absences, so that administrators can build an access structure that genuinely matches their organization.
Why Do Users and Roles Matter in Whitevision?
How Do Roles Affect the Document Workflow?
Because Whitevision routes every document, whether it is a purchase invoice, an expense claim, or a contract, through a defined workflow, the roles assigned to each user determine what happens at every stage of that process. A submitter needs the ability to upload or scan documents, an approver needs visibility into pending items awaiting a decision, and an administrator needs broader access to configure categories, workflows, and integrations. Without this structure, documents could easily end up unassigned, delayed, or approved by someone without the appropriate authority.
What Happens If Roles Are Not Configured Properly?
If roles are poorly defined, several predictable problems tend to appear. For example, documents may sit unapproved because no one was assigned responsibility for them, or an employee without the right permissions may attempt to approve a document that should have gone through a manager instead. Therefore, taking the time to configure users and roles carefully at the start of implementation helps avoid these issues before they affect daily operations.
Which User Roles Are Typically Configured in Whitevision?
What Are the Core Role Types?
While the exact structure can be adapted to an organization’s needs, most Whitevision environments are built around a small set of core roles:
| Role | Primary Responsibility |
|---|---|
| Submitter | Uploads documents or submits expense claims |
| Approver | Reviews and approves, rejects, or questions documents |
| Administrator | Configures workflows, categories, and integrations |
| Finance/Processing user | Books approved documents into the ERP or accounting system |
A single person can hold more than one role. Because of this, smaller organizations often combine responsibilities in one person. Larger organizations tend to separate these roles more strictly, since doing so gives them better internal control.
How Do These Roles Interact with Each Other?
In practice, a document typically moves through a sequence of people. It starts with a submitter, passes through one or more approvers, and ends with a finance or processing user who confirms the booking. Whitevision B.V. Declaraties‘ approval flow is completely tailored to an organization’s existing work process, so this sequence doesn’t need to follow a rigid template. Instead, administrators can configure the exact order and combination of roles to match how their organization already handles approvals. This means the organization doesn’t have to adjust its processes to fit the software.
How Do You Create and Configure a New User?
What Information Do You Need Before Adding a User?
Before adding someone to the system, it helps to gather a few pieces of information in advance. This includes their full name, email address, department or cost center, and the role or roles they will need. If the user will be an approver, it’s also worth confirming any monetary thresholds or document categories they are authorized to handle.
What Are the Typical Steps to Set Up a New User?
- Log in to Whitevision with an administrator account.
- Navigate to the user management section of the portal.
- Add the new user’s details, including their name, email, and department.
- Assign the appropriate role or combination of roles.
- Link the user to any relevant approval chains, cost centers, or document categories.
- Confirm the user has access to the mobile app if they will be submitting or approving documents while away from a desktop.
Afterward, it is good practice to ask the new user to log in and confirm their access works as expected, since catching a misconfiguration early is far easier than resolving it after documents have already started moving through their workflow.
How Do You Configure Approval Permissions and Thresholds?
Why Should Approval Rights Be Tied to Specific Limits?
Not every approver should necessarily be able to approve documents of any value. Because of this, many organizations configure monetary thresholds that determine when a document requires additional review. For instance, a department manager might be authorized to approve expense claims up to a certain amount. Anything above that threshold is automatically escalated to a director or finance lead. This structure helps maintain financial control. At the same time, it means that not every document has to pass through the most senior approver, regardless of size.
How Do You Structure Multi-Level Approval Chains?
For higher-value or higher-risk documents, a single approval step is often not enough. To configure a multi-level chain, administrators typically:
- Define the first approver based on department or document category
- Set a threshold at which a second approver is automatically added
- Decide whether approvals must happen in sequence or can occur in any order
- Configure what happens if any approver in the chain rejects or questions the document
Because these chains can be adjusted at any time, organizations are not locked into a rigid structure and can refine it as their approval needs change.
How Do You Manage Backup Approvers and Temporary Access?
Why Is Planning for Absences Important?
Even a well-configured approval chain can stall if the assigned approver is on leave, sick, or otherwise unavailable. Since documents left waiting for a single unavailable person can quickly create a backlog, it is advisable to configure backup approvers as part of the initial role setup rather than treating it as an afterthought.
How Do You Set Up a Backup Approver?
Typically, configuring a backup approver involves:
- Identifying a suitable colleague with the appropriate authority and familiarity with the relevant documents.
- Assigning them as a backup within the approver’s profile or the relevant workflow settings.
- Setting the timeframe during which the backup should be active, if the system allows scheduled coverage.
- Confirming that notifications and reminders are also routed to the backup during that period.
As a result, documents continue moving through the approval process even when the primary approver is temporarily unavailable, which helps prevent the kind of delays that often occur with manual, paper-based approval methods.
How Do You Maintain Users and Roles Over Time?
When Should You Review Existing User Accounts?
Because staff join, leave, and change positions regularly, user accounts and roles should not be treated as a one-time setup. It is generally good practice to review access whenever an employee changes departments, takes on new approval responsibilities, or leaves the organization, since outdated access can create both inefficiencies and security risks.
How Do You Handle Role Changes and Departures?
When someone changes roles or departs, administrators should promptly update their permissions to reflect the change. This typically includes:
| Situation | Recommended Action |
|---|---|
| Employee changes department | Update cost center and approval chain assignments |
| Employee is promoted to manager | Add approver role and relevant thresholds |
| Employee goes on extended leave | Assign a backup approver for the duration |
| Employee leaves the organization | Deactivate the account and reassign pending approvals |
Since Whitevision is low-code by design, most of these adjustments can be made directly by an administrator without requiring technical support, which keeps the process manageable even for organizations with frequent staffing changes.
Conclusions
Setting up users and roles in Whitevision B.V. Declaraties involves more than simply creating accounts; it requires thinking through submitter, approver, and administrator responsibilities, configuring approval thresholds and multi-level chains where needed, and planning for backup coverage during absences. Although this setup takes some initial coordination between finance, IT, and department leads, the result is a workflow where documents consistently reach the right person without unnecessary delays or oversight gaps. By reviewing user accounts and role assignments regularly, organizations can ensure that Whitevision B.V. Declaraties continues to reflect their actual reporting structure as staffing and responsibilities evolve.
Frequently Asked Questions
Yes. Since roles such as submitter, approver, and administrator are not mutually exclusive, a single user can be assigned more than one role, which is particularly common in smaller organizations where staff often take on several responsibilities at once.
When a user’s account is deactivated, any documents still awaiting their approval should be reassigned to another approver as part of the offboarding process. Administrators are generally advised to check for pending items before deactivating an account, so that no document is left unattended in the workflow.
Administrator access should typically be limited to a small number of trusted staff, such as finance leads or IT personnel, since this role can configure workflows, categories, and integrations that affect the entire organization. Restricting this access helps reduce the risk of accidental misconfiguration while still allowing day-to-day submission and approval tasks to be handled by a broader group of users.
