Gatey is a server-free WordPress plugin that adds Amazon Cognito login and SSO in minutes. Drop in its Authenticator block, shortcode or CSS class—no coding required.

Does Gatey store any user data or client secret?

No. Gatey never stores your Cognito client secrets or your users’ personal data on the WordPress server. All authentication happens directly in the browser against your own Cognito User Pool. The plug-in only keeps non-sensitive settings (e.g., User Pool ID) in WordPress and does not proxy, log, or persist any JWT tokens or profile details.

Is my data shared with any third party?

Gatey never shares your personal data or WordPress site data with any third party. Authentication flows run directly between your site and your AWS Cognito user pool. If you enable premium features, subscription management is handled securely via Stripe using hosted forms and client‑side JavaScript. No payment data is stored or processed by Gatey.

Will it still work after a static export?

Yes. Because all authentication runs in the browser, Gatey talks straight to Amazon Cognito and keeps working even when WordPress is served as static files (Netlify, S3, CloudFront, etc.).

Do I need AWS or Cognito knowledge to use it?

Only the basics. You’ll create a Cognito User Pool and App Client in the AWS console—that’s it. Gatey then takes over all front-end work — sign-in, sign-up, MFA, profile fields—through a visual block or shortcode, no coding required.

How long does setup take?

Usually less than five minutes: install, drop the block, paste your User Pool ID, App Client ID, and region.

Can I show or hide content based on the logged‑in user?

Yes. You can use shortcodes or CSS variables like --gatey-account-group-admin or --gatey-account-attribute-email to control visibility.

Is Gatey compatible with my theme?

Yes. Gatey uses standard Gutenberg blocks and shortcodes, so it works with any WordPress theme or builder (Elementor, Divi, etc.).

Do I need to register or subscribe to use Gatey?

No. Gatey works fully offline out of the box and requires no registration or subscription to function. You can configure your AWS Cognito user pool directly inside WordPress and use login, registration, MFA, and profile features without ever connecting to wpsuite.io. Premium features are entirely optional and only become available after connecting your site using secure client‑side JavaScript.

What’s the difference between plans?

Free includes all core blocks, but frontend customizations are hidden. Basic shows custom blocks on live pages. Professional unlocks social login, JWT/IAM‑secured APIs, and advanced Gatey control.

Where are the subscription-based configuration files stored, and how often are they refreshed?

All Pro settings you create in the Gatey Settings—API Settings, custom Form Fields—are saved server-side and, whenever you hit Save, an encrypted copy is written to your site’s wp-content/uploads/ folder. The small licence file needed to decrypt that config are also stored in uploads. A licence is valid for one month, so the plugin automatically downloads a fresh file every seven days while your subscription is active. If you run a static export, you’ll still need that weekly refresh (a short tutorial covers this topic), but a normal WordPress install handles it for you automatically.

Can I cancel or upgrade later?

Yes, at any time. The plugin will still work in Free mode, and your site’s blocks won’t break — only premium features will deactivate.

Gatey Shortcodes, CSS Vars & JS API Reference

Gatey Reference

Dynamic shortcodes, CSS variables & a secure JS API for authentication-aware UI

Gatey Front‑End Reference

Welcome to the complete Gatey front-end reference manual—your one-stop list of every shortcode, dynamic CSS variable, JavaScript helper, DOM event, and Redux field.

1. WordPress Shortcodes

`gatey`

Embeds a Cognito‑powered <Authenticator> wherever you like—inside a post, a popup, or an Elementor template.

Attribute	Accepted values	Explanation
`id` (required)	Gutenberg pattern ID	Tells Gatey which saved Gutenberg pattern—containing an `<Authenticator>` block—to render. Not meant for DOM‑event targeting; if you need a hook for JavaScript listeners, give the rendered element a normal CSS `id`.
`screen`	`signIn`, `signUp`, `editAccount`, `setupTotp`, `forgotPassword`, `changePassword`	Initial Authenticator screen.
`variation`	`default`, `modal`	Inline widget or modal overlay.
`colormode`	`light`, `dark`, `system`	Force colour scheme or follow OS preference.
`language`	`ar` – Arabic, `de` – German, `en` – English (default), `es` – Spanish, `fr` – French, `he` – Hebrew, `hi` – Hindi, `id` – Indonesian, `it` – Italian, `ja` – Japanese, `ko` – Korean, `kr` – Korean (legacy), `nb` – Norwegian Bokmål, `nl` – Dutch, `pl` – Polish, `pt` – Portuguese, `ru` – Russian, `sv` – Swedish, `th` – Thai, `tr` – Turkish, `ua` – Ukrainian, `zh` – Chinese	Sets the UI language. Specify any of the codes above to lock the interface locale, or omit the attribute to let the browser/OS preference decide automatically.
`direction`	`auto` – Auto (default), `ltr` – Left-to-Right, `rtl` – Right-to-Left	Sets overall text flow.
`showopen`	`true`, `false`	If `true`, renders a button first; clicking it opens the Authenticator with the configured `screen`. Defaults to `false`.
`open`	Free‑text string	Replaces the default label on the open button (defaults to the Authenticator header) when `showopen` is enabled.
`signingin`	Free‑text string	Message displayed while the Authenticator is in the signing‑in state (fires with `signing-in.gatey-authenticator`). Empty by default.
`signingout`	Free‑text string	Message displayed while signing out (fires with `signing-out.gatey-authenticator`). Empty by default.
`redirecting`	Free‑text string	Message shown during the post-login or post-logout redirect if a redirect URL is configured (fires with `signed-in.gatey-authenticator` and `signed-out.gatey-authenticator`). Empty by default.

`gatey-account`

Outputs a Cognito user‑attribute in place—perfect for personalised greetings, user dashboards, or conditional content.

Attribute	Accepted values	Explanation
`component`	`div`, `p`, `span`, `h1`, `h2`, `h3`, `h4`, `h5`, `h6`	The HTML tag Gatey should render for the output. Use a heading, block or inline element to match your layout. Defaults to `div` if omitted.
`attribute`	Any standard Cognito field (e.g. `email`, `given_name`) Literal `custom` for non‑standard.	The profile field you want to print.
`custom`	Name without the `custom:` prefix	Required only when `attribute="custom"`.

Usage examples

gatey id="12" variation="modal" colormode="dark"

Welcome back, gatey-account attribute="given_name"!

Your tier: gatey-account attribute="custom" custom="membershipTier"]

2. Dynamic CSS Custom Properties

Gatey injects these variables on :root. Use them to toggle visibility (flex/none) or print Cognito data via content.

Initialisation flags

--gatey-initialized / --gatey-not-initialized

Editor mode

When a page is open in Elementor or Gutenberg, Gatey sets --gatey-in-editor to flex so those elements remain visible inside the editor even if they would be hidden on the live site—making them easier to edit:

body.elementor-editor-active,
body.wp-admin,
body.block-editor-iframe__body {
  --gatey-in-editor: flex;
}

Authentication & MFA

--gatey-account-authenticated / --gatey-account-not-authenticated
--gatey-account-mfa-enabled / --gatey-account-mfa-not-enabled

Group membership

For every Cognito group <g> Gatey outputs:

--gatey-account-group-<g>
--gatey-account-group-not-<g>

Cognito attributes

--gatey-account-attribute-email
--gatey-account-attribute-family_name
Customs: --gatey-account-attribute-custom-<attr>

/* Visible only to admins */
.admin-panel{
  display:var(--gatey-account-group-admin);
}

/* Show element while editing */
.show-in-editor-or-if-authenticated{
  display:var(--gatey-in-editor, var(--gatey-account-authenticated, none));
}

3. JavaScript API (`Gatey.cognito.*`)

All helper methods live on the global Gatey.cognito object (available after the DOM finishes loading); each one returns a Promise, so use await or .then().

Helper	Returns	Use case
`getUsername()`	string	Display the username
`getUserAttributes()`	object	Prefill a form with profile data
`getMfaPreferences()`	object	Show MFA status
`clearMfaPreferences()`	void	One-click TOTP disable
`isAuthenticated()`	boolean	Guard a route or action
`isInGroup("admin")`	boolean	Role-based UI
`getGroups()`	string[]	Render a badge list
`getRoles()`	string[]	IAM role switcher
`getScopes()`	string[]	Scope-aware buttons
`getPreferredRole()`	string	Auto-select a role
`setLanguage("en")`	void	Switch the Authenticator’s UI language at runtime
`setDirection("ltr")`	void	Override the layout direction (`auto`, `ltr` or `rtl`)
`signOut()`	void	Custom logout button
`getAmplifyConfig`	object	Debug current Amplify settings
`get / post / …`	any	Signed API calls through `aws-amplify/api`

// Sample signed API call
const orders = await Gatey.cognito.post({
  apiName: "backend",
  path: "/orders",
  options: { body: { status: "OPEN" } }
});
console.table(orders);

In the Gutenberg editor, any “Custom Block” element inside the Authenticator block—such as an <a> tag or <button>—can use the onclick attribute with toSignIn(), toSignUp(), or toForgotPassword() to switch directly to the Sign In, Sign Up, or Forgot Password screens.

4. DOM Events from <Authenticator>

Every event is emitted under the name pattern
<type>.gatey-authenticator—for example
done.gatey-authenticator or
cancel.gatey-authenticator.
Give your <Authenticator> (or shortcode)
an id, then attach a listener with
addEventListener.

Event type (before `.gatey-authenticator`)	When it fires
`done`	Screen finished (e.g. password changed)
`cancel`	User pressed Cancel / Back
`signing-in`	Cognito login done, WP login still running
`signed-in`	All hooks finished → redirect
`signing-out`	Hooks + WP logout executing
`signed-out`	Fully signed out → redirect
`reset`	Authenticator re-appears (e.g. code prompt)

// Example listener
const authEl = document.getElementById("login-widget");
authEl.addEventListener("done.gatey-authenticator", () => {
  toast.success("Profile updated!");
});

5. observeStore() – Watch Redux State

The Redux store is exposed asynchronously as Gatey.cognito.store
(a Promise). When it resolves, pass the store to
Gatey.cognito.observeStore along with a selector and a
callback:

// Reload the page if the visitor signs out
Gatey.cognito.store.then((store) =>
  Gatey.cognito.observeStore(
    store,
    (state) => state.signedIn,
    (signedIn, prev) => {
      if (prev !== undefined && !signedIn) {
        window.location.reload();
      }
    }
  )
);

Common selectors:

state.amplifyConfig — ResourcesConfig returned by Amplify
state.signedIn — true | false
state.account — object containing:
- username
- userAttributes
- mfaPreferences

Gatey Shortcodes, CSS Vars & JS API Reference

Gatey Reference

Gatey Front‑End Reference

1. WordPress Shortcodes

`gatey`

`gatey-account`

Usage examples

2. Dynamic CSS Custom Properties

Initialisation flags

Editor mode

Authentication & MFA

Group membership

Cognito attributes

3. JavaScript API (`Gatey.cognito.*`)

4. DOM Events from <Authenticator>

5. observeStore() – Watch Redux State

Navigation

Follow Us:

Gatey Shortcodes, CSS Vars & JS API Reference

Gatey Reference

Gatey Front‑End Reference

1. WordPress Shortcodes

gatey

gatey-account

Usage examples

2. Dynamic CSS Custom Properties

Initialisation flags

Editor mode

Authentication & MFA

Group membership

Cognito attributes

3. JavaScript API (Gatey.cognito.*)

4. DOM Events from <Authenticator>

5. observeStore() – Watch Redux State

`gatey`

`gatey-account`

3. JavaScript API (`Gatey.cognito.*`)