Connections

Connect a tool, such as Power BI or Excel, to your organisation’s Lacroo reports. Each connection has one token and reads only the groups you turn on. It can only read.

Open Org → Integrations. The page has three tabs: Connections, Activity and Guide.

The Guide tab explains everything on the page, next to the controls it describes: how to connect Power BI and Excel, what each group holds, every table and column, and your connection details ready to copy.

Who can use it

Anyone who can view Integrations sees Connections and Activity, and makes their own tokens on Your access tokens. Anyone who can manage Integrations also connects tools, changes their access, and replaces or revokes any token.

Both need organisation-wide access (Master Admin or Organisation Manager by default). A token can never reach Integrations itself, so no token can make more tokens.

Connect a tool

1. On Connections, choose Connect a tool.
2. Pick what you’re connecting: Power BI, Excel or Something else.
3. Turn on the groups it should see.
4. Choose All projects (this includes projects added later) or Choose projects.
5. Turn on anything extra the reports need: Prices, Contact details or Diversity details.
6. Name it, and choose when it expires: In 1 year, In 6 months or Never.
7. Check the summary and choose Create connection.

The last screen shows the token, the feed address and the tool’s steps. Copy the token now: it is shown once. If you close it before copying, Lacroo asks you to confirm.

Nothing is made until you choose Create connection. Up to 50 connections can be live at once, and each needs its own name.

What each group holds

Every group except Lists starts on.

Each group’s tables are listed under Scopes, and each table’s page names its group: see Report tables.

Prices and personal details

All three start off. Leave them off unless the reports need them.

• Prices: rates, costs and budgets. With it off, the reports still send every row, with money columns blank.
• Contact details: workers’ phone, email and post code.
• Diversity details: gender, date of birth, Aboriginal or Torres Strait Islander status, and language.
• Workers’ other answers are sent only when both are on.
• Every time personal details are sent, it shows in Activity.

A connection never sees more than the person who sets it up. A group or switch for something you can’t see in Lacroo is off, and says why.

Send setup to IT

Send setup to IT emails the token to whoever connects the tool, so you don’t have to pass it on yourself.

1. When the token is shown, choose Send setup to IT.
2. Enter IT’s email. Add their name and a note if you like.
3. Choose Send.

IT gets an email from Lacroo with your organisation’s connection details, the connection’s name, access, projects and expiry, and a link. For a Power BI or Excel connection, it also has that tool’s setup steps. The link shows the token once, hidden until IT chooses Show: opening it uses it up. It works for 3 days. Replies to the email come to you.

The connection’s row then shows who it went to and whether they opened it:

• not opened yet: choose Cancel link to stop it.
• opened: the token has been shown. If IT says they didn’t open it, choose Replace token.
• link expired or link cancelled: the link no longer works. Choose Replace token to send a new one.

Replacing or revoking the token cancels its link. Sending the same token again cancels the earlier link. Your organisation can send 20 links a day.

Edit access

Edit access changes a connection’s groups, projects, extra details and name. The token stays the same, so the tool keeps working: its next refresh uses the new access.

Turning a group off asks first. Remove those reports from the tool before you save, or its refresh fails.

A connection that shows Custom access doesn’t use groups yet. Edit access starts at the nearest groups, and saving switches it to them after you confirm.

Replace token and revoke

• Replace token makes a new token, shows it once, and stops the old one at once. The tool stops working until the new token is pasted in. The new token lasts a year, or never expires if the old one didn’t.
• Revoke stops the token for good. It cannot be undone.

Expiry

A token expires in 1 year (the default), in 6 months, or never. 30 days before a token expires, Lacroo emails the person who made it (or, if they have left, the organisation’s Integrations managers). To keep it working, choose Replace token and paste the new token into the tool.

A token also stops working when:

• it is replaced or revoked;
• the person who owns a personal token leaves the organisation or is made inactive, and it stays stopped even if they come back;
• your organisation is suspended.

Your access tokens

Your own tokens, for your own scripts and tools, are on Your access tokens (the key at the bottom of the sidebar). Choose New token, then choose groups, projects and extra details as for a connection.

A personal token sees only what you can, narrowed by what you choose. Administrators see it on Connections, marked Personal, and can revoke it.

Activity

Activity shows, for the last 7, 30 or 90 days:

• Requests: per token, how many requests it made, how many failed, and when it was last used.
• Personal details shared: every time contact or diversity details were sent to a token.

Activity is kept for 400 days.

Using a token

Send the token in the Authorization header on every request, either as a bearer token:

Authorization: Bearer lcr_live_…

or with Basic authentication, using any username and the token as the password (useful for tools such as Power BI and Excel that only offer a username and password):

curl -u "anything:$TOKEN" https://api.lacroo.ai/v1/me/credential

Never put a token in a URL: a request with a token in the query string is refused.

The call above checks a token and tells you what it is:

{
  "credential": {
    "id": "…",
    "name": "Power BI",
    "kind": "service",
    "token_prefix": "lcr_live_AbCd",
    "scopes": [],
    "tool": "power_bi",
    "access": {
      "groups": ["alerts", "diaries", "dockets", "issues", "workforce"],
      "prices": false,
      "contact_details": false,
      "diversity_details": false
    },
    "project_ids": null,
    "expires_at": "2027-10-27T00:00:00Z",
    "created_at": "2026-10-27T00:00:00Z"
  },
  "owner": { "id": "…", "name": "Power BI", "kind": "service" },
  "org": { "id": "…", "name": "Harbourside Civil" }
}

For admins: tokens made in a preview start lcr_test_; tokens made in production start lcr_live_. Each environment accepts only its own, so a production token never works against a preview and a preview token never works in production.

What a token can reach

A token reaches only the operations listed in the API reference. Anything else answers 404, as if it did not exist. A table in a group the token doesn’t have answers 404 too. Contact and diversity details are only filled in when the token has those switches on, and money columns only when Prices is on.