skills.rest
gamedevpl
gamedevplOFFICIAL
Explore all skills by this author →
WebsiteGitHub

managing-beta-participants

Manage closed beta participant access across Firestore records and GitHub environment allowlists.

7|23|Updated Aug 9, 2015
Search Tags:#firestore#allowlist#waitlist#access management#access tokens#closed beta#github variables
One-click install
npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill managing-beta-participants
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: managing-beta-participants
Source: https://github.com/gamedevpl/www.gamedev.pl/tree/main/.claude/skills/managing-beta-participants
Command: npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill managing-beta-participants

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies closed beta access management by helping administrators approve, reject, pre-approve, inspect, and revoke participant access across Firestore and environment-based allowlists.

Core Features & Use Cases

  • Firestore Approval Management: Approve users dynamically by email, reject access, or reset participants to pending without requiring a redeployment.
  • Allowlist Administration: Manage bootstrap email and UID allowlists through GitHub repository variables and understand when deployment is required.
  • Access Auditing: Inspect waitlist records, account verification requirements, and bot access tokens to identify the complete set of accounts that can reach the API.
  • Use Case: Approve a waitlisted user by email, pre-approve a user who has not visited the site, or revoke an automation account's tokens when access must be fully removed.

Quick Start

Use the beta participant management skill to approve [email protected] for closed beta access and verify the resulting access path.

Frequently Asked Questions about managing-beta-participants

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I approve a waitlisted user for closed beta access in Firestore?▼

Closed beta access is approved in Firestore by updating the user's waitlist record by email, ensuring email verification checks are complete without requiring a redeployment.

Can I pre-approve a user who hasn't visited the site yet?▼

Pre-approving a beta participant who hasn't visited the site involves adding their email or UID directly to the bootstrap allowlist managed through GitHub repository variables.

How do I audit which accounts and automation tokens can reach my API?▼

Auditing API access involves inspecting Firestore waitlist records, account verification requirements, and separate bot access tokens to identify the complete set of authorized accounts.

Do I need to deploy my application after updating GitHub environment allowlists?▼

Updating bootstrap email and UID allowlists through GitHub repository variables requires deployment awareness, as some changes mandate a redeployment to apply environment variable updates.

What's the best way to revoke an automation account's access tokens?▼

Revoking an automation account's access tokens requires removing their specific bot credentials and updating the access management records to ensure access is fully removed from the API.

Related Skills

Explore More Software Engineering Skills→
whmathews15whmathews15
1

beta-status

Retrieve activated beta feature status, versions, and activation dates.

Community
Basic
JasragsJasrags
1

mcp-guide

Select and configure MCP servers for AI-assisted project management.

Community
Basic
sumik5sumik5
1

developing-firebase

Guide Firebase development covering authentication, Firestore, Cloud Functions, and Hosting.

Community
Advanced
isamuisamu
45

firebase-security-review

Audit Firebase and Vue applications for security vulnerabilities in Firestore, Storage, App Check, and hosting.

Community
Advanced