# Clerk dashboard access for Replit project — is Replit Pro required? **URL:** \ **Category:** Workspace\ **Created:** [October 21, 2026, 10:18pm UTC](https://replit.discourse.group/t/clerk-dashboard-access-for-replit-project-is-replit-pro-required/13784 "2026-10-21T22:18:02Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dev1674](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dev1674](https://replit.discourse.group/u/dev1674)\ **Post date:** [October 21, 2026, 10:18pm UTC](https://replit.discourse.group/t/clerk-dashboard-access-for-replit-project-is-replit-pro-required/13784/1 "2026-10-21T22:18:02Z")
Hi Replit Community, We are the developers of the Replit project at: [https://replit.com/@arifvoraji/Licence-Card-Game-1](https://replit.com/@arifvoraji/Licence-Card-Game-1) This project uses Replit’s Clerk Auth integration. We need to access the Clerk dashboard (Build → Tools → Users & Auth → Configure → Advanced → “Open Clerk dashboard”) to configure Native API settings for a published Android app. When we click “Open Clerk dashboard”, a “Replit Pro Plan” upsell modal appears instead of opening the dashboard. Questions: 1. Is Replit Pro (or higher) the only way to access the Clerk dashboard for a Replit-managed Clerk instance? 2. 1. If the project creator (Replit username: arifvoraji) upgrades to Pro, will they immediately gain access to this instance’s Clerk dashboard? 3. 1. Is there any other way for the project owner to access or manage the Clerk instance without a Pro plan — for example, by logging into the Clerk dashboard directly? 4. 1. Is it possible to detach or transfer the Replit-managed Clerk instance to a standalone Clerk account? We are not asking for a plan upgrade recommendation — we need to understand the technical options. Contact: [dev@synapzgroup.net](mailto:dev@synapzgroup.net) Thank you. ---
**Author:** ![dev1674](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dev1674](https://replit.discourse.group/u/dev1674)\ **Post date:** [October 21, 2026, 11:57pm UTC](https://replit.discourse.group/t/clerk-dashboard-access-for-replit-project-is-replit-pro-required/13784/2 "2026-10-21T23:57:56Z")
**Update: Clerk Support Response** We contacted Clerk support directly (ticket submitted via the Replit project owner’s account, [jedsy2001@gmail.com](mailto:jedsy2001@gmail.com)) and received the following confirmed response from Jordan at Clerk Support: > “Replit applications create a Clerk application automatically. These are managed by Replit directly. You will not have access on your own Clerk account.” This confirms that our production Clerk instance (Frontend API domain: `clerk.licencerummy.com`, publishable key prefix `pk_live_`) is managed exclusively by Replit — and our inability to access the Clerk dashboard via our own Clerk account is expected behaviour. **We therefore need Replit to assist with one of the following:** **Option 1 — Unlock Clerk dashboard access** for the project owner (Replit username: arifvoraji) without requiring a Pro plan upgrade. Since Replit created this Clerk instance automatically on behalf of our project, we need a supported way to configure it. **Option 2 — Confirm whether upgrading to Replit Pro grants access to the _existing_ production Clerk instance** — specifically, the same instance with the same `pk_live_` key and existing user data intact. Not a new instance. **Option 3 — Apply these three settings on our behalf** to the production Clerk instance (`clerk.licencerummy.com`): - Enable Native API - Register Android application: package name `com.licencerummy.app`, SHA-256 fingerprint `BA:9F:A9:8C:69:B5:AE:DD:E7:A1:01:D4:81:F4:3D:76:2A:B4:A0:0F:FF:37:2B:35:2F:75:EA:8E:C8:0C:39:BA` (from Google Play App Signing) - Add allowed redirect URI: `licence-mobile://sso-callback` These settings are required for our published Android app (`com.licencerummy.app`) to complete Clerk authentication on the Play Store. Our code is already correct and ready — this is purely a dashboard configuration task. **Important:** We do not want a new Clerk instance created, and we do not want the existing publishable key changed. We need to retain the existing instance and all its registered user data. Contact: [dev@synapzgroup.net](mailto:dev@synapzgroup.net)