Back to Applyer
Guide Navigation▾

Admin Guide

Learn how to manage plans, prompts, feature flags, audit logs, and user oversight across the platform.

1. Plans & Features

Goal: Configure subscription plans (Free, Pro, Enterprise), define features with type-safe defaults, and manage entitlement overrides - so every user gets exactly the access they should have.

Steps

  1. Create or edit a plan - Navigate to Admin > Plans. Each plan (Free, Pro, Enterprise) defines a bundle of feature entitlements. Set the plan name, Polar product ID, and monthly price.
  2. Add features with typed defaults - Each feature has a key, display name, and a default value. Value types are boolean (on/off), numeric (e.g. monthly credit limit), or JSON (complex config). The default applies to any plan that does not set an explicit value.
  3. Configure the PlanFeatureMatrix - The matrix shows every plan as a column and every feature as a row. Toggle or set values per plan. Changes take effect immediately for all users on that plan.
  4. Understand the override hierarchy - Entitlements resolve in order: user-level override > plan-level value > feature default. Use overrides sparingly for special cases like beta testers or partnership deals.
Tip: The override hierarchy (override > plan > default) means you can grant a single user Pro-level access to one feature without changing their plan. Use the user detail page to set per-user overrides.
Screenshot: admin-plans-features.png

2. Prompt Management

Goal: View, edit, and version AI prompts used across the platform - with cache invalidation and A/B testing support to iterate safely.

Steps

  1. Browse prompt versions - Navigate to Admin > Prompts. Each prompt is identified by a slug (e.g. cv_optimize_v3) and shows the active version number, last-edited date, and author.
  2. Edit a prompt - Click a prompt to open the editor. Changes create a new version automatically - previous versions are preserved in the history and can be restored at any time.
  3. Invalidate the prompt cache - After saving, click "Invalidate Cache" to push the new version live immediately. Without invalidation, the old version may serve for up to 5 minutes due to caching.
  4. Review version history - The history tab shows every version with diffs. Use this to understand what changed and when. Each AI call logs the prompt version used, so you can trace results back to the exact prompt.
  5. Set up A/B testing - Assign traffic splits between two prompt versions. Results are tracked per version so you can compare output quality before promoting a winner.
Tip: Every AI call logs the prompt version in its metadata. If users report unexpected results, check the prompt history first - a recent edit may be the cause.
Screenshot: admin-prompt-management.png

3. Feature Flags

Goal: Toggle features on or off without redeploying - enabling safe rollouts, instant rollbacks, and gradual feature releases.

Steps

  1. View all flags - Navigate to Admin > Feature Flags. The table shows each flag name, current state (enabled/disabled), and description. Global flags affect the entire platform; per-feature flags target specific functionality.
  2. Toggle a flag - Click the toggle to enable or disable a flag. The change is saved immediately. No deployment or restart is needed.
  3. Understand the 5-minute cache - Flag values are cached for 5 minutes on the server. After toggling, allow up to 5 minutes for all users to see the change. This avoids excessive database reads while keeping response times fast.
  4. Use flags for safe rollouts - Before releasing a new feature, ship the code behind a flag in the disabled state. Enable it when ready, and disable immediately if issues appear - no rollback deploy required.
Tip: If you need a flag change to take effect faster than 5 minutes, trigger a cache clear from the admin panel or redeploy. For most cases the 5-minute window is acceptable.
Screenshot: admin-feature-flags.png

4. Audit Log

Goal: Review a chronological record of admin actions across the platform - with filtering and pagination to quickly find what changed and who changed it.

Steps

  1. Open the audit log - Navigate to Admin > Audit Log. The log shows the most recent actions first, with each entry displaying the admin user, action type, target resource, and timestamp.
  2. Filter by user, action, or date - Use the filter bar to narrow results. You can filter by the admin who performed the action, the action type (e.g. plan_update, flag_toggle, user_credit_adjust), or a date range.
  3. Navigate with cursor pagination - The log uses cursor-based pagination for performance. Click "Next" and "Previous" to page through results. Each page loads quickly regardless of total log size.
  4. Understand log entries - Each entry includes a before/after snapshot where applicable. For example, a credit adjustment shows the old and new credit values. Use this detail to investigate issues or verify changes.
Tip: Audit log entries are immutable - they cannot be edited or deleted. This ensures a reliable record for compliance and troubleshooting.
Screenshot: admin-audit-log.png

5. User & Tenant Oversight

Goal: View and manage users, tenants, credit balances, and enrollment status - with super admin controls for platform-wide oversight.

Steps

  1. Browse users - Navigate to Admin > Users. The user list shows name, email, current plan, credit balance, and last active date. Use the search bar to find specific users by name or email.
  2. Adjust credits - Open a user detail page and click "Adjust Credits." Enter the amount (positive to add, negative to deduct) and a reason. Credit adjustments are logged in the audit trail.
  3. Manage tenants - Navigate to Admin > Tenants to see all organizations. Each tenant shows its type (agency or company), member count, and active job listings. Click into a tenant to manage memberships and settings.
  4. Handle tenant enrollments - The enrollments tab shows pending, active, and revoked enrollments. Approve or reject pending enrollments, and revoke access when a user leaves an organization.
  5. Super admin role - The super admin (identified by the SUPER_ADMIN_EMAIL environment variable) has full access to all admin features. Only one super admin exists per environment. All other admin capabilities require explicit role assignment.
Tip: Credit adjustments use a rolling 30-day window. When adjusting credits, keep in mind that the user's monthly allowance resets based on their plan, not the calendar month.
Screenshot: admin-user-tenant-oversight.png