Ron360 Reports permissions and configuration
Access to Ron360 Reports is governed by four independent things: a feature flag, an organization configuration, a system switch, and per-user permissions. All four must line up before a user sees the feature.
Access gates
Gate | What it is | Effect when off |
|---|---|---|
Ron360 Reports feature flag | A platform flag evaluated before anything else | The user is redirected to the home screen. Indistinguishable from missing permissions. |
RTAAI | Organization-level configuration enabling AI features | Ron360 Reports is unavailable regardless of permissions. |
AI chat assistant system switch | The site switch governing AI assistant surfaces | The route does not resolve. |
AI Reports View | Per-user permission | The Ron 360 Reports navigation item is not shown. |
Because the feature flag is checked before permissions, a user whose organization does not have Ron360 Reports enabled sees exactly what an unauthorized user sees. When diagnosing "I can't find Ron 360 Reports", confirm the configuration and the flag before adjusting the user's role.
Permissions
Permission | What it allows |
|---|---|
AI Reports View ( | Open Ron360 Reports; view, run, and export reports you own or that are shared with you, and RTA standard reports. |
AI Reports Add ( | Build new reports, and copy any report you can read, including shared and RTA standard reports. |
AI Reports Edit ( | Edit reports. Only effective on reports you own. |
Ownership
Permissions decide what actions exist for you at all. Ownership decides which reports you may use them on, and it is tracked per report.
Action | Requires |
|---|---|
Run, export | View permission |
Copy | Add permission, works on any readable report, owned or not |
Edit | Edit permission and ownership |
Move, Schedule, Share, Delete | Ownership |
A report shared with you is not owned by you. Neither is an RTA standard report. For both, Copy is the only way to get a version you can change: the copy is yours outright.
Reports that are read-only for everyone live in the RTA Reports folder, see Folder and report types.
Data scope
Ron360 Reports respects the facilities and data a user is entitled to. Two rules apply, and they point in different directions:
Situation | Whose access applies |
|---|---|
A user opens a report shared with them | Theirs. The report runs against the facilities they can see, so results may differ from the owner's. |
A scheduled report is emailed out |
|
A scheduled report is emailed out: The schedule owner's. Recipients, including addresses outside Fleet360, receive a snapshot generated with the owner's access.
When a recipient is a Fleet360 user, the scheduled report is generated with that user's own data access. Reports sent only to an email address are generated with the schedule owner's access.
The second rule matters when scheduling to external recipients. See Schedule report delivery.
Public export links
Files delivered to external email recipients download through a public, token-based link that requires no sign-in. Anyone holding the link can retrieve that file. Treat delivery links as sensitive.
AI credits
Building and editing reports consumes AI credits. When the organization's allocation is exhausted, new builds fail with "AI credit limit reached, contact your administrator." Existing reports continue to run, export, and deliver on schedule.