Skip to main content

Company Settings in Roubler – Overview for Account Administrators

Audience

This article is for Account Administrators and system owners who:

  • Configure Company Settings in Roubler

  • Need an overview of each Company Settings tab and when to use it

Before you start

  • Make sure you are logged in with an Administrator‑level permission group that can access Settings → Company Settings.
  • Agree internally who owns decisions for:
    • Rostering rules (Operations/Store leadership)
    • Onboarding and workflows (HR/People & Culture)
    • Security and MFA (IT/Security)
    • Clocking and rounding (HR/Payroll/Operations)
  • Where possible, test changes on a single location or group before applying them account‑wide.

Company Settings tabs and what they are used for

From Settings → Company Settings, you’ll see these tabs on the left‑hand menu:

Company Details

Use this for high‑level company information.

Typical use:

  • Maintain the company name displayed in Roubler.
  • In some environments, additional identifiers (e.g. internal reference codes) may appear here.

Admins use this when:

  • Your organisation name changes (rebrand, legal name change).
  • You want the correct name to appear in the Roubler header and system screens.

Roster

Controls global rostering behaviour.

Typical use:

  • Set default roster period views (e.g. week start day).
  • Configure high‑level roster behaviour such as:
    • How open/unassigned shifts are handled.
    • Rules that affect how rosters interact with timesheets and costs.

Admins use this to keep roster configuration consistent across locations and aligned with operational rules.

Onboarding

Controls company‑level onboarding behaviour (separate from specific onboarding workflows).

Typical use:

  • Configure:
    • When and how onboarding notifications are sent to managers or admins.
    • General rules for new starters (e.g. what is required before they become Active).
  • Align system behaviour with HR policies for starting new employees.

Admins use this with HR to ensure onboarding is standardised and supports compliance.

Features

Enables or disables major modules across your account.

Typical use:

  • Turn Broadcast Messaging on or off for your organisation.

  • Control availability of other feature flags as they are released.

Admins use this to roll out or retire features in a controlled way, instead of enabling them ad hoc per user.

Rounding Rules

Defines time rounding rules used for clockings and/or timesheets.

Typical use:

  • Set how clock‑in/out times are rounded (e.g. to the nearest X minutes, or up/down according to policy).
  • Ensure rounding behaviour is consistent with payroll and industrial instruments.

Admins configure this with Payroll to keep paid time aligned with agreed rounding rules.

Business Intelligence

Controls analytics and BI‑related settings.

Typical use:

  • Configure access to business intelligence dashboards or exports (for example, which data sets or metrics are available).
  • Align Roubler data outputs with external BI/reporting tools.

Admins and analytics owners use this to make sure reporting is accurate and secure.

Workflows

Manages system workflows and automated processes.

Typical use:

  • Configure global workflow rules, such as:
    • Who receives certain system notifications or approvals.
    • How particular automated steps behave (for example, onboarding or document workflows at a global level).

Admins use this to keep workflow logic centralised and reduce manual steps for managers and HR.

Security

Controls security policies at company level.

Typical use:

  • Configure Multi‑Factor Authentication (MFA/2FA) behaviour:

    • Admin‑level users must use MFA; you can extend this to other permission levels depending on account setup.

  • Adjust other security‑related options as made available (e.g. session behaviour, password settings).

Admins and IT/Security teams use this to ensure Roubler access complies with internal security standards.

Clocking

Defines company‑wide clocking behaviour.

Typical use:

  • Decide whether employees can select a clock‑in location (useful when one device covers multiple sub‑locations).
  • Control whether Primary Location is used in timesheets when no rostered shift exists.
  • Turn on core clocking options that affect mobile clocking, web clock, and the Clock App.

Admins configure this with HR/Payroll/Operations to make sure clocking behaviour matches policy and pay rules.

Theme

Controls look and feel / branding of Roubler.

Typical use:

  • Set brand colours, logos and other basic visual settings so Roubler matches your organisation’s branding.

Admins or marketing/system owners use this to provide a consistent branded experience for employees.

Frequently asked questions and troubleshooting

1. “I can’t see the Company Settings screen or some tabs”

  • Make sure you are logged in as an Account Administrator (or equivalent high‑level permission group).
  • If you still can’t see it, your permissions may have been restricted; contact your internal Roubler/system owner to review your permission group and locations.

2. “Changes I made in Company Settings are not showing for managers/employees”

  • Some changes apply from the next use or period (e.g. new roster rules, rounding rules), not retroactively.
  • Ask affected users to refresh, log out and back in.
  • For settings that relate to pay (Rounding Rules, Clocking, Security), confirm with Payroll which pay run or date range they should apply from.

3. “I’m not sure which Company Settings tab to use for a change”

As a simple guide:

  • Rostering behaviour → Roster
  • Onboarding experience → Onboarding
  • Enabling/disabling big features → Features
  • How clock‑in times behave → Rounding Rules and Clocking
  • Security/MFA policies → Security
  • Branding → Theme

If a change might affect pay or compliance, confirm with HR/Payroll/IT before proceeding.

4. “I changed something and now behaviour looks wrong”

  • Note:
    • Exactly what you changed,
    • When you changed it, and
    • Example employees/locations affected.
  • If safe, revert to the previous setting while you investigate.
  • Escalate via your internal process (see below) with screenshots and examples.

Who to contact for help

  1. Internal HR / Payroll / People & Culture
    • For:
      • Decisions about rostering, rounding, onboarding and clocking rules.
      • Ensuring Company Settings align with agreements, policies and legislation.
  2. Internal Roubler/System Administrator or IT team
    • For:
      • Security/MFA, feature toggles and workflow design.
      • Permission issues (unable to see or edit parts of Company Settings).
      • Coordinating system‑wide changes and testing.
  3. Roubler Support
    • Should be contacted only by your authorised internal administrators.
    • When raising a ticket, include:
      • Company name.
      • The exact Company Settings tab and fields changed.
      • Screenshots and at least one example (employee/location, expected vs actual behaviour).

This ensures Company Settings remain controlled, auditable and aligned with your organisation’s HR, payroll and security requirements.