Tip: Start typing in the input box for immediate search results.
-
Quick Start
-
- What is Fieldcode?
- Definitions
- What are tickets, projects and workflows?
- How to log in to Fieldcode
- What is the Fieldcode Support Panel?
- What are components?
- What are views?
- Ticket statuses and their meaning
- Ticket colors and their meaning
- Map symbols and their meaning
- Frequently Asked Questions
- Setting up Fieldcode
-
-
Release Notes
-
Short Overview
-
Fieldcode Work Place
-
-
- How to schedule tickets
- How to search for tickets
- How to expert-search for tickets
- How to filter for tickets
- How to grab/ungrab tickets
- How to link & unlink components together
- How to download ticket data as a excel sheet
- How to copy filters/queries for colleagues
- How to email filters/queries to colleagues
- How to assign/unassign tickets to partners
- How to manage spare parts
- How to show tickets on Map
- How to use the Clipboard
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer in the Timeline
- How to schedule tickets
- How to publish tickets to engineers from the Timeline
- How to lock/unlock tickets
- How to manually reschedule PUDOs
- How to show tickets on Map
- How to manage availabilities
- How to manage subgroups
- How to display an additional time zone
- How to move tickets back to the Ticket Pool
-
-
-
- How to use the Interaction buttons
- How to assign/unassign tickets to partners
- How to manage spare parts
- How to use the Workflow buttons
- How to use the Ticket info button
- How to use the Email button
- How to use the Comment button
- How to schedule tickets
- How to use the Remove Pending button
- How to cancel a ticket
-
Fieldcode Admin Panel
-
- What is the Process menu?
- What is the Workflows menu?
- How to create & edit projects
- Automated Actions in the overview
- How to setup custom Automated Actions
- How to setup pre-configured Automated Actions
- How to create & edit conditions
- How to create & edit indications
- How to set up email templates
- How to create & edit ticket durations
- How to create & edit custom fields
- How to create & edit custom forms
- How to create & edit value sets
- How to create & edit SLA Profiles
- How to move stuck tickets via Ticket Workflow Monitoring
-
- Articles coming soon
-
Fieldcode Mobile App
-
Fieldcode Customer Portal
How to create & edit permissions
The permissions menu gives you the ability to specify exactly what a user is authorized to do in the tools.
You can add and edit roles in the Permissions menu.
How to create new roles
- Go to the Fieldcode Admin Panel -> Permissions.
- Click the plus button to open the New user form.
- Fill in or edit the following tabs: Basic, Security Resources, Filters, and Users.

1. Basic tab
- Decide if your new or existing role should be active in the system.
- Insert a name for your new or existing role.
- Insert a description for your new or existing role.

2. Security resources tab
You can now decide if you want to start with an empty role or edit an already existing one.
If you select an empty role you have to set permissions for all areas of all our three applications manually.
If you select a preset, like, let’s say for example the engineer preset, you can edit already existing permissions to your particular needs and create a new role out of it.
Set checkmarks for the permissions you want to grant.
You can decide between two permission sets and grant them per application:
View permissions: Allows the selected role to view something on his system (eg. a component the role needs for his workflow).
Edit permissions: Allows the selected role to interact with something on his system (eg. interact with the Ticket Pool component).
You also have the possibility to bulk-permit permissions by selecting a group of permissions.
Bulk permissions will be displayed with the black-filled box.

3. (Optional - only custom roles) Filters tab
You are able to add optional ticket filters to set permissions for specific tickets.
The Assigned toggle lets you set that users will only see tickets assigned to them.
Let’s assume you want to assign a role for all tickets from a certain project – you would pick something like:
Condition = ProjectName
Operator = is equal to
Comparison Value = Demo Project
Let’s assume you want to assign a role for all tickets from a certain country – you would pick something like:
Condition = AffectedCountry
Operator = is equal to
Comparison Value = Germany

4. (Optional - only custom roles) Filter buttons tab
You can restrict the visibility of some buttons for your custom role. This could be for example useful if you don’t want to overwhelm a new dispatcher with unnecessary buttons that might not be helpful for him to fulfill the job.
By default, all buttons are visible, if you don’t assign buttons to the right side.
However, as soon as you assign one button to the right, only the right-assigned button will be visible for the role.

5. Users tab
In the next step, you assign your users to the role. This is done by drag & drop or clicking on the user you want to add to the role.
You are also able to bulk-add or bulk-remove users by using the buttons.
If you cannot find a user or the list is too big, you can also search for specific users by inserting a keyword into the search bar.
