العربية

Start free trialBook a demo

Browse the documentation

Documentation

All appsHow the apps connectTeam workflowsCompare

Apps

HR ManagementRecruitment (ATS)Payroll & WPSTime & AttendanceAccounting & E-InvoicingCRM & Sales PipelineSales Orders & FulfilmentInventory, Purchasing & WarehousingProcurement & TendersConstruction & ContractingContracts & E-SignatureProducts & Online StorePoint of SaleRentalsSubscriptions & LicensingHelpdesk & TicketingSocial Media SuiteInfluencer Marketing & Campaign ROIProject ManagementActivities WorkspaceDocument ManagementPDF Tools & E-SignatureCorrespondence RegisterTeam Chat & CallsMeetings & VideoLearning & Certification (LMS)Asset ManagementFleet ManagementRecognition & GamificationContacts & PartnersNotification CentreReports & DashboardsInsights — Business Intelligence & AppsAI CopilotAI Agents & AutomationAI Diagram StudioWebsite BuilderISO Compliance Suite (Imtithal)App MarketplaceCustomer & Partner PortalSecurity, Access & Compliance

Support role guides — what each role can do, step by step

What a person sees when an action fails — the five-second message, Copy details and Open ticket — and how a company administrator reads what went wrong for everyone, in one list. 12 steps across 2 roles, every one of them carried out in the product before it was published here.

Last updated

Nothing matches that. Try a shorter word, or pick All roles to search every guide.

Go deeper

Anyone at work

When something fails, the screen says what happened and what to do next.

Reads what a failed action says, copies the details for whoever helps, and opens a support request from the message in one click.

What you will be able to do

  • Read what failed, and whether the fault is ours
  • Copy the details so nobody has to ask you for them
  • Open a support request from the message, already filled in
  • Know that a failure on our side is recorded even if you do nothing
  • Find the answer yourself on the Support page: search, topics, common questions

What this role can and cannot do

CanCannot
  • Read what failed and why, in your own language
  • Copy the details of a failure for whoever helps you
  • Open a support request from the message, already filled in
  • Search the help, read a topic and the common questions on the Support page
  • See what went wrong for people in the company (Settings » Errors)
  • Mark a problem resolved, or open it again, with a note

8 steps, each one carried out in the product on .

Read what the message tells you #

Where Any page, top right corner

  1. Open your company's address in the browser — it looks like yourcompany.tarleaks.com.
  2. Type the e-mail address your administrator set up for you, then your password.
  3. You land on the app launcher: a grid of the apps your company uses.
  4. Do your normal work. When an action fails, the message appears at the top right.
Screenshot: Read what the message tells you, Anyone at work view
Top right: a red-edged message. The first line says what failed. A line starting “Sorry — something went wrong on our side” means the fault is ours and we have been told. The last line is the reference.

You should see The message says what failed. When the fault is on our side it starts with an apology and says we have been told. Under it is a reference — the one thing support needs from you.

Watch out The message goes after five seconds. Resting the mouse on it keeps it. If you missed it, do the action again — the same message comes back.

Worth knowing The message leaves on its own after five seconds unless the mouse is on it. Press Copy details or Open ticket before it goes.

Copy the details for whoever helps you #

Where The message » Copy details

  1. On the message, press Copy details.
  2. Paste (Ctrl V, or ⌘V on a Mac) into the place you are asking for help.
Screenshot: Copy the details for whoever helps you, Anyone at work view
The button turns into “Copied” for two seconds.

You should see What you copied is plain text: what failed, the reference, the page you were on, the time and the version of the app. It never holds a password or a sign-in.

Watch out Paste before you copy anything else — the clipboard holds one thing at a time.

Open a support request from the message #

Where The message » Open ticket

  1. On the message, press Open ticket.
  2. Read the title and the description that are already filled in.
  3. Type one sentence at the top of the description, then press Send.
What each field wants
FieldWhat to put in it
TitleAlready filled in from the message. Change it if you can say it better.
Tell us moreStarts with a line and then the details block — the reference, the page, the time. Add what you were trying to do above it.
What's this about / How urgentLeave the first on “Not sure”; pick the urgency that matches your work.
Screenshot: Open a support request from the message, Anyone at work view
A new support request with the details already in the description.

You should see The request carries the reference, so support finds the exact failure without asking you to repeat anything.

Watch out Do not delete the details block. Support searches by the reference in it.

A refusal says what to change, with no apology #

Where The message

  1. Do the thing that is not allowed.
  2. Read the message.
Screenshot: A refusal says what to change, with no apology, Anyone at work view
The same message, without the apology line. The sentence says why it was refused.

You should see An apology appears only when the fault is on our side. When the system refuses what you asked, the message tells you what to change instead, and says nothing about being sorry.

Watch out If the reason does not make sense to you, use Copy details or Open ticket — the details carry the reason word for word.

The company's error list is for administrators #

Where Settings » Errors

  1. Open Settings. There is no Errors entry in your menu.
  2. If you open its address (/settings/errors) you are told you have no access.
Screenshot: The company's error list is for administrators, Anyone at work view
“You don't have access to this section.” This is the correct answer for you.

You should see Only a company administrator can read what went wrong across the company. Your own failures are still recorded, and they reach that list.

Watch out If you need to see the list, ask your company's administrator for the role that includes it.

Search the help before you ask #

Where Support » Search

  1. Open Support (the life-ring at the top right, or Support in the launcher).
  2. Type a word — leave, say — in the search box.
  3. Pick a tab: All, Guides, FAQ or Team workflows. The results line says how many answers the chosen tab holds; a question opens its answer in place.
Screenshot: Search the help before you ask, Anyone at work view
The words you searched for are highlighted in each answer, and the address keeps the search and the tab, so a refresh or a pasted link shows the same list.

You should see The words you searched for are highlighted in each answer, and the address keeps the search and the tab, so a refresh or a pasted link shows the same list.

Read a help topic without leaving the page #

Where Support » Help topics

  1. Under Help topics, pick an app — Time & Attendance, say — then a topic.
  2. The topic opens in the reader: what it covers, the team workflows, the questions customers ask, and the apps it works with.
  3. Use previous / next to walk the app's topics.
Screenshot: Read a help topic without leaving the page, Anyone at work view
The help is the product's own documentation, in English or Arabic as you use the app; on a phone the topic list is a drawer.

You should see The help is the product's own documentation, in English or Arabic as you use the app; on a phone the topic list is a drawer.

The common questions, and a ticket if they do not answer you #

Where Support » Frequently asked questions

  1. Below My tickets, open a question.
  2. If the answer does not help, press Still stuck? Open a ticket.
Screenshot: The common questions, and a ticket if they do not answer you, Anyone at work view
The new ticket starts with the question as its title and names the guide you read, so nobody has to ask what you already tried.

You should see The new ticket starts with the question as its title and names the guide you read, so nobody has to ask what you already tried.

Use cases — the work, step by step

Each one is a sequence somebody actually performs, with the screen behind every step. Every screen here was opened in the product as this role before it was published.

urgentSomething failed while you were working #

You should not have to describe a failure from memory. The message already holds what support needs, and it takes ten seconds to hand over.

  1. Read the message. If it starts with an apology, the fault is on our side and we have been told; if it names a reason, that is what to change.

    Anyone at work doing "Something failed while you were working" in Tarleaks ERP — Read the message. If it starts with an apology, the fault is
    Any page, top right corner — verified: the page says “Sorry — something went wrong on our side”; the page says “Reference:”; the page says “Copy details”; the page says “Open ticket”
  2. Hold the mouse on the message so it stays, then press Open ticket.

    Anyone at work doing "Something failed while you were working" in Tarleaks ERP — Hold the mouse on the message so it stays, then press Open t
    The message » Open ticket — verified: the control is offered; the field already holds “Reference:”; the field already holds “Page:”
  3. Add one sentence about what you were doing and press Send. Support now has the page, the time and the reference.

    Anyone at work doing "Something failed while you were working" in Tarleaks ERP — Add one sentence about what you were doing and press Send. S
    The message » Open ticket — verified: the control is offered; the field already holds “Reference:”; the field already holds “Page:”

urgentAsk a colleague or your administrator for help instead #

Sometimes the quickest help is the person next to you. The details travel with you either way.

  1. Press Copy details on the message before it goes.

    Anyone at work doing "Ask a colleague or your administrator for help instead" in Tarleaks ERP — Press Copy details on the message before it goes.
    The message » Copy details — verified: the page says “Copied”
  2. Paste it into the chat or e-mail to the person helping you.

    Anyone at work doing "Ask a colleague or your administrator for help instead" in Tarleaks ERP — Paste it into the chat or e-mail to the person helping you.
    The message » Copy details — verified: the page says “Copied”

You never have to remember what you clicked. The page, the time and the reference are in the message, and your company's administrator can see what went wrong for your colleagues too.

Company administrator

See what went wrong for your people in one list, without waiting for anybody to report it.

Sees what went wrong for people in the company — the page, who it happened to, when — and marks each problem resolved once it is dealt with.

What you will be able to do

  • See each kind of problem once, with how often and for how many people
  • Open one to see who it happened to, where and when
  • Mark it resolved, and know if it comes back
  • Choose whether failures are recorded at all

What this role can and cannot do

CanCannot
  • See what went wrong for people in the company (Settings » Errors)
  • Mark a problem resolved, or open it again, with a note
  • Switch company features on and off, including error recording
  • Nothing in this list is closed to this role.

4 steps, each one carried out in the product on .

See what went wrong for people in your company #

Where Settings » Errors

  1. Open Settings.
  2. Choose Errors.
Screenshot: See what went wrong for people in your company, Company administrator view
Three tiles on top (Open, Came back, Resolved), then one row per kind of problem. The line above the list says how many failures were recorded in the last 24 hours.

You should see One row per kind of problem, newest first. A problem that happens to ten people ten times is one row, not a hundred lines.

Watch out A problem that is Resolved and then happens again turns into “Came back”. That is the one to read first.

Open one: who, where, when, and the reference #

Where Settings » Errors » a row

  1. Click a row in the list.
Screenshot: Open one: who, where, when, and the reference, Company administrator view
A window with the problem on top, then a table: when, the person (name and e-mail), the page, the reference, and the browser with the version of the app.

You should see Each line is one time it happened. The person is named, the page is the one they were on, and the reference is the number support searches for.

Watch out People's names and e-mail addresses are shown here, so opening a problem is recorded in the audit log.

Mark it resolved, with a note #

Where Settings » Errors » a row » Mark as resolved

  1. Open a row.
  2. Write what was done in the note.
  3. Press Mark as resolved.
What each field wants
FieldWhat to put in it
NoteWhat you did or learned, in a sentence. It stays with the problem and is shown to the next person who opens it.
Screenshot: Mark it resolved, with a note, Company administrator view
The button changes to “Open again”, and the row moves to Resolved.

You should see The row moves to Resolved. If the same problem happens again it comes back marked Came back, so a fix that did not hold is not missed.

Watch out Resolved is your own marker. It does not change what the vendor sees.

Switch error recording on or off #

Where Settings » Features

  1. Open Settings.
  2. Choose Features.
  3. Type “record errors” in the search box.
  4. Find “Record errors so they get fixed” under General.
Screenshot: Switch error recording on or off, Company administrator view
One switch. Off stops this company's failures being recorded; it does not hide the message people see, and Settings » Errors shows nothing while it is off.

You should see The company decides. Off means failures are no longer recorded for your company and Settings » Errors says “Error recording is turned off for this workspace” until the switch is on again; on is the default.

Watch out Leave it on unless there is a reason: it is how a problem is found before anyone has to report it.

Use cases — the work, step by step

Each one is a sequence somebody actually performs, with the screen behind every step. Every screen here was opened in the product as this role before it was published.

weeklyMonday check: what went wrong last week #

A problem nobody reports is a problem nobody fixes. One list shows every failure your people hit, whether they said anything or not.

  1. Open Settings » Errors and read the three tiles first: anything marked Came back is a fix that did not hold.

    Company administrator doing "Monday check: what went wrong last week" in Tarleaks ERP — Open Settings » Errors and read the three tiles first: anyth
    Settings » Errors — verified: the control is offered; the page says “What went wrong”
  2. Open the row with the most people. Read who it reached and on which page.

    Company administrator doing "Monday check: what went wrong last week" in Tarleaks ERP — Open the row with the most people. Read who it reached and o
    Settings » Errors » a row — verified: the page says “Latest times it happened”; the page says “Reference”
  3. When it is dealt with, write what was done and press Mark as resolved.

    Company administrator doing "Monday check: what went wrong last week" in Tarleaks ERP — When it is dealt with, write what was done and press Mark as
    Settings » Errors » a row » Mark as resolved — verified: the page says “Open again”

The list is your company's own. Nothing from another company is ever shown here, and the people it names are your own colleagues.