user-feedback: Temporary Access setup misses feature-preview activation step
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- postgresql
- Domain
- documentation
Research direction
Start in SKILL.md under “Core Principles > Supabase changes frequently” and “Supabase Documentation,” then review the relevant Temporary Access changelog entry. Add the feature-preview troubleshooting note and organization-level activation guidance, including that the Database Settings section may be absent until the preview is enabled. Done when the documented Postgres version or plan is no longer presented as sufficient for UI visibility.
Written by the indexing model from the issue text.
Description
What happened
Task: Configure Supabase Temporary Access / JIT database role mapping when the documented dashboard section was not visible.
Skill said: The skill routes agents to current documentation, and the documented dashboard path led the agent to advise looking for Database Settings → Enable temporary access. That section was absent even though the project met the documented Postgres version requirement.
Expected: For feature-preview functionality, the skill should explicitly tell agents to check the feature's changelog entry for any organization-level activation step before concluding that a dashboard section should be present. Temporary Access currently requires enabling its feature preview before the project-level UI appears.
Source
File: SKILL.md
Section: Core Principles > Supabase changes frequently and Supabase Documentation
Fix suggestion
Add a feature-preview troubleshooting note: when current docs describe a dashboard control that is missing, check the relevant changelog entry for an organization-level preview flag or activation URL. For Temporary Access, mention that the org feature preview may need to be enabled before the Database Settings section appears. Do not infer that Postgres version or project plan alone guarantees UI visibility.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/agent-skills
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
supabase/agent-skills#586 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#585 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
supabase/agent-skills#583 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
supabase/agent-skills#582 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#581 ·
All issues in supabase/agent-skills
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100