This section covers who may do what in ILAP Analytics, how a machine authenticates without a person signing in, and the processing that runs behind the interface once a schedule has been posted. It is written for administrators.
What this section covers
- Roles — Admin, Writer and Reader: what each may do, and how a role is assigned to a user or group.
- Access tokens — how an external system, such as a planning tool or an integration, submits data securely without an interactive sign-in.
- Background jobs — the work that runs after an ILAP file arrives: storing schedules and activities, building revisions, and preparing data for analysis.
- Health dashboard — whether ILAP Analytics and the services it depends on are working.
Why these are documented together
They are the two things to check when someone reports that data has not arrived. Either the submitter could not get it in — a missing role or an expired token — or it went in and is still being processed, which is what the background jobs and the health dashboard will tell you.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article