Administration¶
Tenant admins manage the setup that makes SLApulse useful for the team.
The Setup area contains:
- Projects
- workspace Settings
- Users
- Billing
Members do not see these routes. They can follow SLA health, triage work, inspect issues, and review reports.
Workspace settings¶
Use Settings to manage:
- workspace name
- default display timezone
- holiday calendars
- holiday overrides
The default timezone is used when a user has not selected a personal display timezone. Timestamps in Command Center, Operations, Analysis, and exports should be read with the displayed timezone.
Holiday calendars¶
Holiday calendars are used by business-hours SLA policies.
You can preview a country or subdivision calendar, save it, and add local closure days when needed.
Example:
| Date | Name |
|---|---|
| 2026-12-24 | Company closed day |
If a project uses that holiday calendar, business-hours SLA time can treat the day as closed.
Users¶
Use Users to invite teammates and choose their role.
| Role | Use it for |
|---|---|
| Admin | People who should change projects, SLA rules, users, billing, or workspace settings. |
| Member | People who should monitor SLA health, triage work, inspect issues, and use reports. |
Keep Admin access limited. Most day-to-day users should be Members.
Inviting users¶
Use this simple flow:
- Create the user with the right email address.
- Choose the lowest role that fits the work.
- SLApulse sends an invitation with the workspace login link.
- The user enters their e-mail address there and uses the short-lived code that arrives by e-mail.
- Ask the user to log in and check that they can see the expected areas.
Do not use shared accounts. Separate users make audit logs and access control easier to understand.
Profile and personal settings¶
Each user can manage their own profile without changing workspace setup.
Use Profile to update:
- display name
- language
- personal display timezone
Tenant users do not create or change a password. They sign in with a short-lived code sent to their e-mail address.
Your personal display timezone changes only how SLApulse shows dates, times, and deadlines to you. It does not change the shared SLA calculation. Each project’s SLA clock continues to follow that project’s SLA policy, including its configured timezone, working hours, and holiday calendar.
This means teammates in different regions can read the same issue events and deadlines in their own local time while still working against the same project SLA commitment.
Profile changes affect only the current user. Workspace defaults, users, billing, projects, and SLA rules still belong in the Admin-only Setup area.
Billing and support¶
Billing is available to tenant admins.
If a plan, payment, or Enterprise agreement needs help, contact contact@slapulse.com.
For plan limits and subscription states, see Subscription and Billing.
Danger zones¶
Danger zones contain destructive actions, such as:
- reset project data
- delete source connection
- delete project
- delete issue
Read the text in the danger zone before using the action. These actions are meant for correction, cleanup, or permanent removal.
Project data reset¶
Reset project data clears imported/runtime data and keeps project setup.
It removes:
- issues
- event history
- source checkpoints
- source job history
It keeps:
- project setup
- webhook secret
- source connection setup
- SLA rules
- issue filter
- status mapping
Reset is blocked while import or reconcile jobs are running.
Use reset when the first import was based on wrong mapping, wrong filters, or a too-short date window. Do not delete the project if the setup is still useful.