Job Collar
Install / connection control

Connect the right sources. Keep control.

Setup is guided, permission-aware and shaped around the sources and write-back pathways approved for each customer.

SETTINGS / AUTHORISED CONNECTIONS Live view
Job Collar connection and branding settings
Connections

What can be connected

JobAdder

The company system of record. Connection and permissions are agreed with the customer before permitted data becomes available.

LinkedIn connections export

A user's permitted connections export can be added through LinkedIn's official export route. Job Collar does not ask for a LinkedIn password or claim to scrape the service.

Outlook or Gmail contacts

A user may connect permitted professional contacts through browser-based authorisation where that connector is enabled for the workspace.

Not every source or connector is enabled for every customer. The agreed workspace setup determines what is available.

First connection

The onboarding sequence

  1. 1

    Open setup

    Launch Your Collar setup from the signed onboarding launcher or the secure link supplied for the workspace.

  2. 2

    Add permitted relationship context

    Follow the official LinkedIn connections export route and, if enabled, choose whether to authorise Outlook or Gmail contacts.

  3. 3

    Review JobAdder authorisation

    Job Collar prepares or opens the authorisation request. The customer reviews it and sends it; requested permissions depend on the agreed setup.

  4. 4

    Wait for approved access

    External approval timing varies. Job Collar starts only when the relevant permitted data is available.

  5. 5

    Begin the first audit trail

    The workspace records source, timing and processing state as the first permitted records and signals are assessed.

Setup itself is designed to feel like following the bouncing ball. The guided steps may take about ten minutes, but third-party authorisation can take longer and is outside Job Collar's control.

JobAdder API authorisation

You review it. You send it. You stay in control.

  1. 1

    Request prepared

    Job Collar prepares a JobAdder API authorisation request shaped to the setup agreed with the customer. It is presented to you — nothing is authorised on your behalf.

  2. 2

    You review what is requested

    The request sets out the access being asked for. The exact permissions and scopes depend on your JobAdder workspace and the approved integration, so review it against your proposal before sending.

  3. 3

    You send it through JobAdder

    The authorisation itself happens inside JobAdder's own process — the customer sends the request and approves it there. Job Collar never asks for your JobAdder password.

  4. 4

    Access stays under your control

    Approved access can be reviewed, adjusted or revoked with JobAdder. If access changes, Job Collar's processing of the affected sources stops accordingly.

The authorisation request is generated for your review — Job Collar does not publish fixed endpoint details, and the exact permissions requested are confirmed in your proposal and reflected in the request you send.

First audit

What happens in the first audit.

Sources confirm available

The workspace waits until the permitted sources you authorised are actually available — Job Collar does not assume access it does not have.

Records assessed with provenance

The first permitted records and signals are assessed, and each one retains its source, timing and processing state so the reasoning can be checked.

Nothing is written without review

The first pass reads and assesses. Any suggested change back to JobAdder waits for human approval, in line with how write-back works everywhere in the product.

You see the starting position

You finish onboarding with a view of what was found in the permitted records — relevant now, possible moves and relationships worth checking — before any action is suggested.

Ownership

Two data estates remain distinct.

Company ATS / CRM data

JobAdder and company-held recruitment records remain company-owned and governed by the customer's permissions and policies.

User-contributed relationship context

Permitted professional sources contributed by a user remain distinct. Any use or portability is subject to entitlement, privacy, employment and contractual obligations.

Security

Authentication stays off the device.

  • No passwords, reusable API keys or persistent OAuth tokens are stored on a USB or physical Collar.
  • Where available, sensitive authorisation happens in the browser through the provider's OAuth flow and can be revoked.
  • A physical onboarding item may hold only a signed launcher and a unique onboarding or customer identifier.
  • The Collar concept has no GPS, tracking or battery unless a future version has a clearly stated reason for one.
Technical behaviour

JobAdder remains the system of record.

Controlled write-back

Notes, tasks or updates use agreed pathways as those pathways are enabled for the workspace.

Human approval

Bulk actions remain reviewable. Approval is a control point, not a claim that a person has audited every row.

Provenance and audit

Important activity can retain its source, timing and processing state so the reasoning can be checked.

Rollback and correction

Mistakes should stay visible and reversible through the controls available for the agreed workflow.

Direct return to source. Where the workspace supports it, Job Collar links an insight back to the current JobAdder record or page so the recruiter can verify and continue there.

Troubleshooting

Common setup checks

JobAdder authorisation is pending

Confirm the customer has reviewed and sent the request. Requested access and approval timing depend on the customer's JobAdder arrangement.

A contact source is not available

Check whether Outlook or Gmail is enabled for the workspace and whether the user completed browser authorisation with the intended professional account.

An expected person or relationship is missing

Check source permissions, export date and matching evidence. Recruitment data is messy; uncertain matches should be reviewed rather than silently forced.

A write-back did not complete

Check whether that pathway is enabled, then review its success, failure or audit state before retrying or rolling back.

Access should be removed

Revoke the provider connection where applicable and contact Job Collar support to confirm the workspace connection state.

Need a hand?

Talk through your setup before connecting anything.

Email demo@jobcollar.com.au or book a guided demo.

How it works