Description
CloseHub Connector replaces the multiple credentials previously required to link a WordPress site with CloseHub — a marketing project management platform.
Once the plugin is activated, it generates a secure API key and exposes a dedicated REST API namespace (/wp-json/closehub/v1/) that CloseHub uses to interact with your site.
It also exposes content abilities through the WordPress MCP Adapter. MCP clients can discover, list, read, create, update, upload an image, update a post slug, replace one exact Gutenberg block, and send posts to the trash using the server at /wp-json/mcp/mcp-adapter-default-server. closehub/upload-media accepts an image as data_base64, returns its Media Library URL, and requires the user’s upload_files capability; pass that URL as featured_image_url to create or update content without uploading a duplicate. closehub/update-post-slug accepts a post ID and slug, then returns the normalized unique slug and resulting URL. closehub/get-post returns a content_hash; use it with closehub/replace-gutenberg-block, a zero-based block_path, the current block name, and one replacement serialized block so a stale read cannot overwrite newer content. These abilities default to the post type but accept a post_type input for any other post type registered with an admin UI — pages, WooCommerce products (including product types WooCommerce’s own MCP abilities don’t support, such as subscriptions), or custom post types. Authenticate with OAuth as a WordPress user, or use the same CloseHub API key as a Bearer token for a shared Claude Team connector. The API key acts with the capabilities of the WordPress user who last generated it.
Settings: One page under Settings → CloseHub (Network Admin → Settings → CloseHub on multisite) shows the API key, the CloseHub endpoint, the MCP server URL, and the user the key acts as. The same API key connects CloseHub and Claude.
Claude Team: In Claude, add a custom connector with the MCP server URL from Settings → CloseHub, choose No sign-in, and add a request header named authorization with the value Bearer <your API key>. The URL uses a ?rest_route= query to help preserve the header when a server rewrite strips it from /wp-json/ requests. Everyone sharing this connector has the WordPress permissions of the user who last generated the key. Regenerating the key disconnects CloseHub and every Claude user until updated. OAuth per-user sign-in remains available under Advanced.
When WPML is active, create-post and POST /closehub/v1/posts also accept language and an optional translation_of source post ID. The connector assigns the new post to the requested language and joins it to the source post’s translation group. List/get/create responses include the language and translation-group details. Existing posts retain their language on update.
When TranslatePress is active instead, the language abilities (list-languages, add-language, set-default-language) manage its languages, and get-post/list-posts/create-post responses return language (the default language the content is written in) and language_urls with the URL of a published post in every published language. TranslatePress translates one post into every language, so language, translation_of, link-translations, unlink-translation, duplicate-post and missing_translation answer with closehub_translatepress_unsupported. If both plugins are active WPML is used.
With TranslatePress, closehub/list-string-translations lists the strings of a post (or every string containing search) with their translation and status per language, and closehub/save-string-translations saves translations for one language as human reviewed, so an MCP client can translate content itself instead of spending automatic translation quota.
For WooCommerce, MCP clients with the manage_woocommerce capability can retrieve an order summary for a date range, including order count, total sales, average order value, and matching orders.
It also exposes a set of “site” abilities for the CLOSE web go-live checklist — configuration steps that used to be manual or wp-cli only. Each requires the WordPress capability noted below.
Available MCP site abilities:
closehub/search-replace-domain(manage_options) — Replaceold_domainwithnew_domainacross post content, options, comments, and meta tables, re-serializing serialized values safely. Skipswp_posts.guid. Passdry_run: trueto preview the number of rows that would change per table without writing anything. Example:{ "old_domain": "staging.example.com", "new_domain": "example.com" }.closehub/set-robots-txt(manage_options) — Writecontenttorobots.txt, physically if the site root is writable, otherwise served virtually through therobots_txtfilter. Example:{ "content": "User-agent: *\nDisallow:\nSitemap: https://example.com/sitemap.xml" }.closehub/set-post-noindex(edit_poston the targetpost_id) — Set or clear the noindex robots meta for one post/page using whichever SEO plugin (Rank Math, Yoast or SEOPress) is active. Example:{ "post_id": 42, "noindex": true }.closehub/flush-permalinks(manage_options) — Regenerate rewrite rules, equivalent towp rewrite flush. Takes no parameters.closehub/get-htaccess(manage_options, read-only) — Return whether.htaccessexists and its current content. Takes no parameters.closehub/set-site-settings(manage_options) — Update the site timezone and/or admin email; at least one is required. Example:{ "timezone": "Europe/Madrid", "admin_email": "client@example.com" }.closehub/reassign-posts-author(edit_others_posts) — Reassign every post ofpost_type(defaultpost) fromfrom_author_idtoto_author_id, with a per-post success result. Example:{ "from_author_id": 3, "to_author_id": 1 }.closehub/install-wp-org-plugin(install_plugins) — Install (without activating) a plugin from the WordPress.org plugin directory byslug. Example:{ "slug": "two-factor" }.closehub/install-plugin-zip(install_plugins; plusupdate_pluginsto replace an installed copy andactivate_pluginswhenactivateis true) — Install a plugin from a base64 zip like Plugins > Add New > Upload Plugin. Only for small zips: deploy real packages withcreate-deploy-ticketbelow. The zip must hold a single folder (slug, when given, must match it). Withoverwrite(defaulttrue) the installed copy is backed up and replaced, like “Replace current with uploaded”. Clears WP Rocket and OPcache. Returnsslug,previous_version,new_version,active,backupandupgrader_messages. Example:{ "filename": "my-plugin.zip", "data_base64": "UEsDB...", "slug": "my-plugin" }.closehub/install-theme-zip(install_themes; plusupdate_themesto replace andswitch_themesto activate) — Same as above for themes, like Appearance > Themes > Add New > Upload Theme.closehub/create-deploy-ticket(install_plugins/install_themes) — Single-use ticket to upload one plugin or theme zip from disk to the returnedupload_url, sent in theX-CloseHub-Deploy-Ticketheader. Bound to the current user,typeandslug; expires in 15 minutes and is burned on first use. The upload installs or replaces the package like the zip abilities. Example:{ "type": "theme", "slug": "my-theme" }.closehub/get-installed-version(activate_pluginsfor plugins,switch_themesfor themes; read-only) — Installedversion,nameandactivestate of one plugin or theme, plus thebackupsavailable for rollback. Example:{ "type": "theme", "slug": "my-theme" }.closehub/rollback-package(install_*andupdate_*for the type) — Reinstall a backup taken before a replace: the most recent one, or thebackupfile named by get-installed-version. The current copy is backed up first. Example:{ "type": "theme", "slug": "my-theme" }.closehub/list-unused-plugins(activate_plugins, read-only) — List installed plugins that are not currently active, as removal candidates. Takes no parameters.closehub/update-plugins-and-core(update_pluginsandupdate_core) — Update every plugin with an available update and WordPress core to the latest version, with a per-plugin success result. Takes no parameters.closehub/create-site-user(create_users, pluspromote_userswhenroleisadministrator) — Create a WordPress user for the site’s client.roledefaults toeditor;usernamedefaults to the local part ofemailwhen omitted. Example:{ "email": "client@example.com", "role": "editor" }.closehub/link-translations(edit_poston both posts) — Link two existing posts as WPML translations without creating or editing content.post_idjoins the translation group oftranslation_of(the original) inlanguage. Rejects a language mismatch, different post types, a non-translatable post type, atranslation_ofthat is itself a translation, and an existing translation in that language (closehub_translation_conflict) unlessforce: true, which detaches it into its own group. Purges the cache of every post in the affected groups unlessclear_cache: false. Example:{ "post_id": 5789, "translation_of": 4732, "language": "en" }.closehub/unlink-translation(edit_post) — Move a translation into a translation group of its own. The original post of a group cannot be unlinked while it has translations.closehub/list-languages(edit_posts) — List the active WPML or TranslatePress languages and the default one;include_available: truealso lists supported languages that can still be added. With TranslatePress each language also reportspublishedand itsurl_slug, and codes are locales such asfr_FR.closehub/add-language(manage_options) — Activate a WPML-supported language by code, e.g.{ "language": "fr" }, or add a language to translate into with TranslatePress, e.g.{ "language": "fr_FR" }(publish: falsekeeps it hidden from visitors; the page cache is purged unlessclear_cache: false). Existing content is not changed.closehub/set-default-language(manage_options) — Make an active language the site default.closehub/duplicate-post(edit_post+ create capability) — Copy an original post into one or more other languages as drafts, using WPML’s own duplication. Each copy is linked to the original by default;link: falsecreates independent, unlinked copies. Example:{ "post_id": 42, "languages": [ "en", "fr" ] }.closehub/create-postwithlanguagecreates new content in that language; addtranslation_ofto link it as a translation of an existing post, or leave it out to keep it unlinked.closehub/clear-cache(rocket_purge_cacheormanage_options) — Purge the page cache of the active caching plugin (currently WP Rocket).scopeisall(default, whole site) orposts(only the givenpost_ids; IDs that don’t match a post are reported back ininvalid_post_ids). Passminify: trueto also clear minified CSS/JS files. Returns503when no supported cache plugin is active. On multisite passsite_idto choose the site to purge; on a subdirectory network, purging the main site with WP Rocket also clears the subsites’ cached pages, since they live inside the main site’s cache folder. Example:{ "scope": "posts", "post_ids": [ 42, 57 ] }.
What it replaces:
- WordPress Application Password (username + password)
- WooCommerce REST API consumer key and consumer secret
- Gravity Forms API key
You only need to share two things with CloseHub:
- Your site URL
- The generated API key (found at Settings → CloseHub)
Available endpoints:
GET /closehub/v1/ping— verify the connectionPOST /closehub/v1/posts— publish or draft a post (or another post type viapost_type), including optional SEO metadata (Rank Math, Yoast or SEOPress), featured image, categories, and WPMLlanguage/translation_ofwhen WPML is activePUT /closehub/v1/posts/{id}— update a post’s (or other post type’s) title, content, excerpt, status, SEO metadata, featured image, or categoriesGET /closehub/v1/woocommerce/orders— fetch order data (requires WooCommerce)GET /closehub/v1/woocommerce/store-stats— best sellers, best customers, new customers, buying hours and unpaid orders (requires WooCommerce)GET /closehub/v1/gravity-forms/forms— list forms (requires Gravity Forms)GET /closehub/v1/gravity-forms/forms/{id}— get form detailsGET /closehub/v1/gravity-forms/forms/{id}/entries— count form entries by date rangePOST /closehub/v1/elm-releases— create an Easy License Manager release for a product (byproduct_idorproduct_sku) and update its WooCommerce download file to the givenzip_urlin one call; optionaltested,requires,requires_php,upgrade_noticePUT /closehub/v1/elm-releases/{id}— update fields on an existing release (all optional) and, ifzip_urlis given, its product’s download file
WooCommerce, Gravity Forms, and Easy License Manager endpoints return a clear error if those plugins are not active — they are not required.
Multisite networks:
MCP abilities work from the network too: connect once with the network API key and every ability knows which sites it can act on. Abilities that read content or rebuild per-site caches (list-posts, list-languages, get-order-summary, flush-permalinks) run on every site and return one result per site; pass site_ids to limit them. Abilities tied to a specific post, file or setting (for example create-post, get-post, update-post, trash-post, set-robots-txt, clear-cache) require a site_id so an ID is never applied to the wrong site. Server-wide abilities (install-wp-org-plugin, install-plugin-zip, install-theme-zip, create-deploy-ticket, get-installed-version, rollback-package, list-unused-plugins, update-plugins-and-core) run once. Use closehub/list-sites to discover site IDs. Permissions are re-checked on every site.
On a WordPress Multisite network, the same endpoints listed above are shared by every site in the network — there is no separate namespace or key to manage. Activate the plugin network-wide and go to Network Admin → Settings → CloseHub to find one API key shared by the whole network. Every request to those endpoints automatically returns a sites array with one entry per site in the network (site_id, url, and that site’s data or an error message), instead of a single site’s result — handy when a network is used to run the same company in multiple languages.
Installation
- Upload the
closehub-connectorfolder to/wp-content/plugins/. - Activate the plugin through the Plugins screen in WordPress admin.
- Go to Settings → CloseHub.
- Copy the Site URL and API Key shown on that page.
- Paste both values into CloseHub under your project’s WordPress connection settings.
FAQ
Where do I find my API key?
Go to Settings → CloseHub in your WordPress admin. The key is displayed there along with a copy button.
Can I regenerate the API key?
Yes. Click Regenerate Key on the Settings → CloseHub page. The old key stops working immediately — update CloseHub with the new key right away.
How do I connect Claude Team when OAuth discovery is blocked?
Go to Settings → CloseHub, copy the MCP server URL, choose No sign-in authentication in Claude Team, and add a request header named authorization with the value Bearer <your API key> (use the Copy button next to the header). Everyone using that connector shares the WordPress permissions of the user shown under Acts as user.
Do I need WooCommerce or Gravity Forms installed?
No. Both are optional. If they are not active, those endpoints return a 503 response with a clear message instead of crashing.
How is the API key secured?
The key is stored in wp_options (or network-wide in wp_sitemeta on multisite), never exposed on the frontend, transmitted only via HTTPS, and verified using constant-time comparison (hash_equals) to prevent timing attacks. It is never logged or included in REST responses.
How do I deploy a plugin or theme zip from my computer?
Call the closehub/create-deploy-ticket ability with type and slug. It returns a single-use ticket, valid for 15 minutes and only for that package, and an upload_url. Send the zip there as multipart/form-data in the file field, with the ticket in the X-CloseHub-Deploy-Ticket header; overwrite, activate and clear_cache go in the query string. No application password is needed: the route accepts only tickets. The plugin repository ships bin/closehub-deploy, a script that does the upload; see docs/deploy.md.
Can I use this plugin on a multisite network?
Yes. When network-activated, the plugin generates one API key shared by every site in the network (managed from Network Admin → Settings → CloseHub instead of a per-site Settings page), and the same REST endpoints automatically query every site and return combined, per-site results. On a regular, non-multisite install, everything works exactly as a single site as described above.
Is this plugin affiliated with WooCommerce or Gravity Forms?
No. It integrates with those plugins using their public PHP APIs but is not developed, endorsed, or supported by WooCommerce or Gravity Forms.
Changelog
1.3.2
- Added
GET /closehub/v1/woocommerce/store-stats: best sellers, best customers (display name only, never the e-mail), new customers, buying hours by weekday and unpaid orders for a date range (requires WooCommerce). - Added TranslatePress support:
list-languagesandadd-languagemanage its languages (including whether each is published and its URL slug),set-default-languageexplains that TranslatePress cannot change its default language without orphaning translations, and post responses includelanguageandlanguage_urls(the URL of a published post in every published language). Adding a language purges the page cache. - Added
closehub/list-string-translationsandclosehub/save-string-translations(TranslatePress,manage_optionsor thetrp_translating_capabilityfilter): list a post’s strings or search site-wide strings with their translation per language (render: truerenders the post in each language first, so TranslatePress registers its strings, and records the strings it parsed on the post: needed with themes such as Divi, where TranslatePress does not link content strings to the post), then save translations byoriginal_idor exact original text as human reviewed. The page cache ofpost_id(or the whole site) is purged after saving. - With TranslatePress active,
language,translation_of,link-translations,unlink-translation,duplicate-postandmissing_translationnow answerclosehub_translatepress_unsupportedinstead of asking for WPML. WPML is used when both plugins are active. - Added the
closehub/list-theme-patternsandclosehub/get-theme-patternMCP abilities: list the block patterns of the active theme, core, plugins and synced patterns as metadata only (optionalcategoryandsearch), then fetch the content of one byslugor syncedid, so a client can build a landing page from existing patterns and save it as a draft withcreate-post. Both requireedit_posts. - Added LiteSpeed Cache support to the
closehub/clear-cacheMCP ability, using LiteSpeed’s publiclitespeed_purge_all/litespeed_purge_postactions. WP Rocket still takes precedence when both are active. - Added SEOPress support for SEO title, meta description, and target keyword on post create/update and read-back, and for the
closehub/set-post-noindexMCP ability. - Tested up to WordPress 7.2.
1.3.1
- Added MCP abilities to install or replace a plugin or theme from a zip (
install-plugin-zip,install-theme-zip), with single-use deploy tickets for large uploads (create-deploy-ticket),get-installed-versionandrollback-packageto restore the backup taken before a replacement. - Added
parent_idtocreate-postandupdate-postfor hierarchical post types such as pages;list-posts/get-postreturn it. - Fixed
PUT /posts/{id}clearing SEO fields that were not sent: only the SEO fields present in the request are updated. - Added
missing_translationtoclosehub/list-posts: with WPML, only return posts whose translation group has no post in that language. - Added
dry_runtoclosehub/link-translationsto preview the current and target translation groups, the post that would be detached and whetherforceis needed, without writing. The ability is now annotated as destructive and reportsleft_in_old_groupwhen a forced move leaves dependent translations behind. - Fixed Codex and other native MCP clients being rejected when their OAuth callback used an ephemeral loopback port, as required by RFC 8252.
- Fixed OAuth PKCE parameters being lost when an authorization request passed through the WordPress login screen.
- Fixed Bearer authentication behind PHP-FPM and reverse proxies that expose the Authorization header outside the standard WordPress server variables.
- Added multisite support to MCP abilities from other plugins (Rank Math, WP Rocket, Imagify, WooCommerce, Meta Box…): on a network they now take a required
site_idand run on that site, so redirections, SEO settings and more can be read and changed per subsite. - Added multisite support to MCP abilities: fan-out across the network or a single site via
site_id/site_ids, per-site permission checks, and a newclosehub/list-sitesability. - Added WPML language management abilities:
list-languages,add-language,set-default-languageandduplicate-post(linked or unlinked copies). - Fixed
closehub/update-postapplying the same post ID on every site of a network. - Changed: on a multisite network
closehub/create-postnow requiressite_idinstead of creating the post on every site when no site was given. - Abilities from other plugins are not run on a subsite where that plugin is inactive, and WPML language changes are refused on a subsite while WPML still has another site’s settings loaded, so they can never overwrite that subsite’s WPML configuration.
duplicate-postcreates its copies as drafts from the start and as independent translations, so editing the original never overwrites them; copies keep no SKU/GTIN and are authored by the acting user.- Added the
closehub/link-translationsandclosehub/unlink-translationMCP abilities to link existing posts as WPML translations.list-postsandget-postnow return every translation (language,post_id,translation_group),list-postshonorslanguagewith WPML (includingall), andcreate-postnow rejectspost_idinstead of silently creating a duplicate.
1.3.0
- Simplified settings into a single page: the CloseHub API key now also authenticates MCP (Claude Team) as a Bearer token, acting as the user who last generated it. The separate
chm_shared token and the API/MCP tabs were removed; Claude Team connectors using achm_token must be updated to use the API key.
1.2.1
- Added a revocable shared MCP Bearer token for Claude Team connections when OAuth discovery is blocked by the web server. The token uses the permissions of its WordPress creator and can be rotated or revoked from the MCP settings tab. (#47)
- Added a query-routed MCP server URL for hosts where the
/wp-json/rewrite drops theauthorizationheader, and made the completeBearer chm_...value copyable for Claude Team setup. (#47) - Split CloseHub settings into API and MCP tabs on single sites and multisite networks. (#47)
1.2.0
- Added WordPress Multilingual Plugin (WPML) support to MCP and REST content creation, including optional language assignment and translation-group linking. (#30)
- Added MCP image uploads from base64 to the Media Library, with validation, quota checks, attachment metadata safeguards, and reuse as a post’s featured image. (#40)
- Added a branded OAuth consent screen that clearly discloses the public CloseHub MCP abilities being authorized. (#41)
- Added the
closehub/clear-cacheMCP ability for supported caching plugins, starting with WP Rocket. (#35) - Fixed CloseHub content and site abilities not being exposed as direct tools by the default MCP server.
- Fixed Claude and other hosted MCP clients that identify themselves with a Client ID Metadata Document: OAuth authorization now validates that document directly when no prior dynamic registration exists, and advertises that capability in the authorization-server metadata. Re-registering the same verified client is idempotent and refreshes its stored metadata instead of failing on a duplicate client ID. (#34)
- Added
POST /closehub/v1/elm-releasesto create an Easy License Manager release and update the product’s WooCommerce download file in one call, unblocking automated premium-plugin releases. Accepts optionaltested,requires,requires_php, andupgrade_notice. Preserves any other downloadable files already on the product instead of replacing them. Returns503if Easy License Manager is not active. (#19) - Added
PUT /closehub/v1/elm-releases/{id}to update fields on an existing release (and its product’s download file) without creating a duplicate release for the same version. - Fixed a crash on PHP 8+ when a route’s numeric
id/product_idargument was validated:is_numericwas registered directly asvalidate_callback, but WordPress calls it with 3 arguments and the internal function only accepts 1. Affected/posts/{id},/gravity-forms/forms/{id}, and both newelm-releasesroutes.
1.1.2
- Fixed MCP OAuth discovery on Apache-managed sites, including reliable handling of the protected-resource and authorization-server metadata routes after activation, URL changes, or regeneration. (#27)
- Added precise Gutenberg block replacement through MCP, with content-hash concurrency protection and block-path/type validation, plus an MCP ability to update a post slug and return its normalized URL. (#29)
1.1.1
- Added 11 MCP “site” abilities covering the CLOSE web go-live checklist: domain search-replace, robots.txt content, per-page noindex, permalink flush,
.htaccessread, timezone/admin email, bulk post-author reassignment, WordPress.org plugin install, unused-plugin listing, plugin/core updates, and client user creation. See the Description section for the full list and required capabilities. - Added
post_typesupport to allclosehub/*-postMCP abilities (list-posts, get-post, create-post, update-post, trash-post) and to the/closehub/v1/postsREST endpoints. They still default topost, but can now read and write pages and WooCommerce products (including product types WooCommerce’s own MCP abilities don’t support, such as subscriptions) instead of only plain blog posts. Allowed post types are limited to ones registered as public and admin-manageable, so internal WooCommerce records such as orders and coupons, and Media Library attachments, are not exposed as generic content. - Fixed: creating a post now checks that post type’s own
create_postscapability, and publishing throughcreate-post/update-postchecks itspublish_*capability (e.g.publish_products), instead of always assumingpost‘sedit_posts/publish_posts. - Fixed: MCP post creation and updates now recheck those capabilities independently on every site in a multisite network before writing, so a denied site reports a per-site error without changing its content.
- Fixed: setting
categorieson a post type that doesn’t support that taxonomy is now rejected before any other change is saved, instead of possibly after the title, content, or other fields were already updated.
1.1.0
- Added an MCP server (OAuth 2.1 + PKCE) so AI clients such as Claude can list, read, create, update, and trash posts and read WooCommerce order summaries with the permissions of a real WordPress user.
- Added a
PUT /closehub/v1/posts/{id}endpoint to update a post’s title, content, excerpt, status, SEO metadata, featured image, or categories. - Fixed: MCP post creation/update no longer lets a user without the
manage_categoriescapability create new categories by naming one that doesn’t exist yet. - Fixed: MCP get-post/list-posts now include the same featured image and SEO metadata create-post and update-post accept.
- Fixed: a dynamic OAuth client registration using a real client_id metadata URL could no longer have its verified name and redirect URI overridden by the request body — closing an impersonation path where a code could be redirected to an attacker-controlled URI while the consent screen showed a trusted name.
- Fixed: the OAuth consent page now sends
X-Frame-Options/CSP headers to prevent it from being framed (clickjacking the Authorize button). - Fixed: an MCP access token could previously authenticate as its user for any WordPress REST route whose query string happened to contain the MCP endpoint path, not just the MCP endpoint itself.
- Fixed: OAuth token responses now send
Cache-Control: no-store; the dynamic client registration endpoint is now rate-limited per IP.
1.0.5
- Fixed: featured images from URLs without a filename extension, including Google Drive download URLs, can now be attached when CloseHub creates a WordPress draft.
1.0.4
- Added support for optional SEO titles, meta descriptions, focus keywords, categories, and featured images when creating posts from CloseHub.
- Added support for saving SEO metadata in Rank Math and Yoast SEO when either plugin is active.
- Improved post creation reliability by completing metadata before publishing and removing incomplete posts when metadata processing fails.
1.0.3
- Fixed: sites that already had an API key configured on a subsite before multisite support was added (<=1.0.1) now keep working after upgrading — the existing key is migrated to the network-wide setting instead of a new one being generated, which previously caused CloseHub requests to fail with 401.
1.0.2
- Added WordPress Multisite network support: one API key shared across the whole network, managed from Network Admin → Settings → CloseHub.
- On multisite, existing endpoints (ping, posts, woocommerce/orders, gravity-forms/*) now return combined results for every site in the network instead of a single site.
1.0.1
- Updated assets.
1.0.0
- Initial release.
- Single API key replaces WordPress Application Password, WooCommerce REST credentials, and Gravity Forms API key.
- Endpoints: ping, posts, woocommerce/orders, gravity-forms/forms.
- Admin settings page at Settings → CloseHub with copy buttons and regenerate key action.
