Account, Sync & Plans
The PromptHub desktop app works offline and does not require an account for local AI asset management. An account is for hosted capabilities such as cloud assets, supported sync workflows, community publishing, and team features exposed by the current client and plan.
When You Need an Account
Section titled “When You Need an Account”- Use a cloud sync or backup flow supported by the current client.
- Open hosted assets in the Web Studio.
- Publish a prompt or skill to Explore.
- Use an enabled team sharing workflow.
- Review plan, capacity, and usage information.
You can stay signed out when you only need local asset management on one device.
Sign-In Methods
Section titled “Sign-In Methods”The public site currently uses third-party sign-in. Depending on deployment configuration, it can show GitHub, Google, and LINUX DO. Sign-in and registration share one entry: the first successful authorization creates an account, and later authorizations with the same identity sign in to it.
A button is usable only when that environment has valid OAuth credentials and an allowed callback URL. Local development requires a provider application that allows the local callback; a production-only callback configuration is not enough.
Compatibility endpoints may remain for verification or migration of historical email accounts, but the current public login page does not offer email-and-password sign-in.
Sync Scope
Section titled “Sync Scope”PromptHub offers several data paths with different purposes:
| Path | Purpose | Boundary |
|---|---|---|
| WebDAV / S3 | Desktop online sync | Uses one selected active sync source |
| Self-Hosted Web | Independent restore snapshots | Automatic jobs upload only; restore is explicit |
| PromptHub Cloud | Official hosted accounts and cloud assets | Object scope and quota depend on the client, service configuration, and plan |
Check the object list shown by the product before enabling a path. Do not assume that every local file, model credential, or private Agent setting is uploaded. Treat anything not explicitly listed as local-only.
Team Capabilities
Section titled “Team Capabilities”The hosted service models workspace access with these roles:
| Role | Access Boundary |
|---|---|
| owner | Manages the team, members, plan, and critical settings |
| admin | Manages members and most team content |
| editor | Creates and edits authorized team content |
| viewer | Reads authorized team content |
Whether a team workflow appears depends on the current client and plan. Do not infer that an operation is publicly available from the role model alone.
Plan Limits
Section titled “Plan Limits”Plans affect hosted resources, not local editing. Limits can include cloud object counts, attachment capacity, sync frequency, team members, and official AI usage. Use the values shown by the pricing, workspace, and checkout pages at the time of purchase.
Practical Advice
Section titled “Practical Advice”- Create a local backup before enabling any sync path for the first time.
- Avoid bulk-editing the same assets on multiple devices at once.
- Remove secrets, customer data, and internal paths before publishing.
- Keep OAuth sign-in, WebDAV, self-hosted snapshots, and official cloud sync conceptually separate.