ServiceFloGuide

Your first hour as an administrator

You have installed ServiceFlo and signed in with the account you made (Install ServiceFlo). This page takes you from that empty site to a service desk that receives email, has people working in it and has one ticket in its queue.

Everything here is under Settings, in the menu on the left. Settings has a search box at the top: type “mailbox” or “team” to jump to a page.

1. Create your first workspace

A workspace is one group’s service desk: its own tickets, teams, queues and settings. IT Support is a workspace; Human Resources or Facilities can each be another later. People only see the workspaces they work in.

A new install has none, so Settings opens with Start by creating your first workspace. Choose Create a workspace and give it:

  • a name, such as IT Support;
  • the name of its first team, the agents who answer its tickets (Service Desk is filled in for you).

That one step makes:

What Why
The workspace, with you as its admin An admin may change a workspace’s settings.
The team, with you as its lead Anyone on a team is an agent: they work tickets.
A queue for the team A queue is a list of tickets agents work from. New tickets land here.
Statuses, priorities and resolution codes The steps a ticket goes through (Open, Waiting on requester, Resolved, Closed) and how urgent it is (Low to Urgent).
A Monday-to-Friday business calendar The hours the service-target clock counts in.

Rename or change any of it later; nothing here is fixed.

2. Make it yours

Three short pages under Settings › Installation:

  • Branding: your organisation’s name and colours.
  • Logos: the logo in the menu and the icon on the browser tab.
  • Usernames and sign-in: what your organisation calls a login name (“Staff ID”, say), and whether visitors must sign in before they see the home page.

3. Choose your modules

Settings › Installation › Modules lists the parts of ServiceFlo. Tickets and Reports are always on. The others can each be switched off: Knowledge Base, Service Catalog, Problems, Changes, Assets, Tasks, Contracts, AI features and Semantic search.

Switching a module off hides its pages and links. It deletes nothing, so you can turn it back on later. A fair start for a small desk is tickets, the knowledge base and the service catalog, with the rest added when you are ready for them.

A workspace can also opt out of a module the installation has on: Settings › Workspace › Workspace details, “Modules this workspace uses”.

4. Add your colleagues

A person needs an account, and a place on a team to work tickets.

Accounts

Open Settings › Workspace › People and choose New person. Give their name, a username and their email address. You can put them on a team in the same step: choose the team, and Member or Team lead.

Leave First password empty and ServiceFlo emails them their username and a link to choose a password. The link works once, for four hours; after that they can ask for a new one with Forgot your password? on the sign-in page. Or type a first password and tell it to them yourself: ServiceFlo never sends a password by email.

Once signed in, anyone can change their password: open the menu under their name (top right), choose Preferences (or Your profile for someone who is on no team) and press Change password.

Someone who forgets their password presses Forgot your password? on the sign-in page and types their email address; a link arrives by email. You can also send it for them: on Settings › Workspace › People, press Email a password link under their name.

These links need outgoing email. Until EMAIL_URL is set (see Install) no email leaves. Until then, type a first password for each new person; and for a forgotten one a superuser sets a new password in the back office: scroll to the end of Settings, open Back office › People, choose the person and use the password form there.

If you connected a directory (Active Directory or LDAP, see directory.md), you do not need New person for people who are in it: typing a person’s username in “A place on a team” below finds them in the directory and makes their account, with their name, email and department filled in. Such an account has no password in ServiceFlo. With LDAP_AUTH_ENABLED=true in .env the person signs in with their directory username and password; they change that password with your organisation, not here.

A place on a team

If you did not choose a team when you made the account, or the person is in your directory:

  1. Open Settings › Teams › Teams and members and choose the team.
  2. Under Members, type the person’s username or email in Add someone, choose Member or Team lead, and press Add.

Being on a team is what makes someone an agent in that workspace: they see its queues and can work its tickets. A team lead can also change the team’s picture.

Two other roles are on Settings › Workspace › People:

  • Admins may change the workspace’s settings. Add a second one, so you are not the only person who can.
  • Reporters may open the workspace’s reports without being agents.

5. Connect a mailbox

A connected mailbox turns each email it receives into a ticket, and each reply into a note on that ticket.

Open Settings › Email and integrations › Inbound mailboxes and choose New mailbox. The parts that matter:

Part What to give
Name and email address A name for your own use, and the address people write to, such as helpdesk@example.org.
Connection IMAP with the server’s host, port, username and password; or Microsoft 365 via Graph API with the tenant id, client id and client secret of an app registration.
After fetch What happens to a message once it is a ticket: mark it read, move it to a folder, or delete it.
Where new tickets go The queue, status and priority new tickets get. Left alone, they go to the workspace’s default queue: your first team’s.

Save it, then send an email to the address. The mailbox is checked about every minute. Back on the list, Last checked and Health show whether the connection worked, and the ticket appears under Queues.

For ServiceFlo to send email (replies and notifications), the server needs the EMAIL_URL setting described in Install ServiceFlo, under “Email”. Until it is set, nothing is sent.

6. Open a ticket yourself

  1. Choose New ticket, at the top right.
  2. In Requester, type a username or an email address: your own will do.
  3. Give it a title, pick a priority, and choose Create ticket.

Open Queues in the menu: the ticket is in your team’s queue. Open it, write a reply, and move it to Resolved. That is the whole path a real request takes.

What to set up next

None of this is needed on day one. Roughly in the order most desks reach for it:

When you want Look under Settings
A form on the web for people to ask for help Tickets › Intake forms
Categories, buildings and other labels on tickets Tickets › Tag fields and Custom fields
Tickets sent to the right team by themselves Automation › Routing and escalation rules
A promise on how fast you answer Automation › Service targets and Business calendars
Ready-made answers Tickets › Canned replies
More lists of tickets (Unassigned, Urgent) Tickets › Queues
Guides people can read on their own Content editor, in the menu
AI summaries, drafts and triage Installation › AI providers, then AI task routes

Before real people rely on the site, set up nightly backups: Backups and upgrades.