Hub configuration
Open Themeatos → Planwise to configure the product.
Routes
| Setting | Default | Purpose |
|---|---|---|
| App route slug | app |
Frontend shell (/app/, /app/projects/, …) |
| Login route slug | login |
Branded login page |
Authentication
- Built-in login — WordPress credentials on
/login/(can be disabled for custom auth). - Required capability — minimum capability after sign-in (default
manage_options). - Allowed roles — optional allow-list; leave empty to allow any role that meets the capability.
Branding
Primary color, accent color, and Google Font family for the app shell. The logo uses the WordPress custom logo when set.
PWA
Enable/disable the progressive web app, name, short name, description, icon, and colors. Manifest and service worker URLs appear under Live URLs.
Notifications
In-app notifications, optional web push / iOS push credentials, prompt-on-login, and which event types are enabled.
SMTP for outbound wp_mail() (host, port, encryption, auth, From address, test send). Optional THEMEATOS_PLANWISE_SMTP_PASSWORD in wp-config.php for production.
Integrations
Hub cards under Integrations submenus: GitHub, Google Drive, and Telegram. Project-level connections are managed inside the app under a project’s Integrations tab. Object storage (Local / Cloudflare R2) is configured under the separate Storage tab.
Telegram
When a bot token is saved, Planwise requires a webhook secret. If you leave the secret blank on first save, one is generated automatically. Inbound webhooks without a valid X-Telegram-Bot-Api-Secret-Token are rejected.
Data on uninstall
Under Data & uninstall, enable Keep Planwise data when uninstalling to retain settings, projects, tasks, and related meta after the plugin is removed.
If that option is off, uninstall removes Planwise options, notification table rows, custom post types (projects, tasks, schedule, activity, comments), and Planwise user meta (plan history, copilot chats, OAuth tokens, web-push subscription).