Settings
Spotlight’s configuration lives on the Settings page - open Apps → Spotlight and pick Settings in the left-hand navigation. The page is Jira-admin only: non-admins opening it see a notice saying so (the current configuration is not shown to them).
Team spotlights - permissions
Section titled “Team spotlights - permissions”The Settings page is a group × capability matrix: one row per Jira group, one checkbox column per capability.
| Capability | What it controls |
|---|---|
| Publish | Who may save a spotlight with “Shared with the team” visibility (and edit their shared spotlights). Publishing also needs View, so nobody can add to a gallery they cannot see. |
| View | Who sees the Team spotlights section of the gallery. |
How the matrix behaves:
- Empty means everyone. A capability with no groups checked is open to the whole site - this is the default. Checking one or more groups restricts that capability to their members.
- Jira admins always retain both capabilities, regardless of the matrix - so a configuration mistake can never lock admins out.
- Use the search field to filter large group lists; up to 50 groups can be checked per capability.
- Click Save permissions to apply. Changes take effect on the next gallery load.
A common setup: leave View open to everyone, restrict Publish to a jira-reporting or team-leads group - everyone benefits from the gallery, a small group curates it.
AI fair use
Section titled “AI fair use”AI drafting is included with the app, with monthly fair-use caps: 150 drafts per user plus a shared site budget of 1,000 AI calls (a draft normally uses one call, occasionally two when Spotlight automatically retries). When a cap is hit, Spotlight says which one; templates and the manual builder are never limited. Details in Draft with AI.
What’s stored where
Section titled “What’s stored where”Spotlight persists to Forge storage (KVS) inside your Atlassian tenant:
| Data | Contents |
|---|---|
| Your private spotlights | Definition (settings/JQL/plan), title, your description, dates |
| Shared spotlights | The same, plus the author’s account ID |
| Permission settings | The group lists for Publish and View |
| AI usage counters | Monthly draft counts (site and per-user) for fair use |
Issue data is never stored. Every render fetches live from Jira. See security for details.
Usage analytics
Section titled “Usage analytics”Spotlight records which features get used, so we know what to improve. It sends your site address, which Spotlight reads from Atlassian rather than from your browser, along with a few counters such as which data source a spotlight uses and whether it was drafted by AI.
Your Jira data, your descriptions and your prompts are never included, and activity is recorded against your site rather than against individual people.
Admins who would rather send nothing can turn this off in Atlassian Administration. Spotlight keeps working exactly as before.
What’s not yet configurable
Section titled “What’s not yet configurable”Sensible roadmap items that aren’t in the current build:
- Changing a spotlight’s visibility in place (today: delete and recreate)
- Per-group or adjustable AI quotas
- Custom fields as chart groupings (today: the seven built-in groupings)
- Site-wide default visibility
If any of these block you, tell us at support@bytera.tech.
- Sharing & Team Gallery - what the capabilities gate.
- Troubleshooting & FAQ - common questions.