Getting started

Overview

P4A — Policies for Agents — is a community-driven catalog of custom policies for the MuleSoft Omni Gateway. The portal lets you:

• Discover policies built by the community: browse the catalog, filter by category, read the source on GitHub, and pick the ones that fit your APIs.
• Submit your own custom PDK policy by pointing P4A at a public GitHub repository — P4A validates the project layout and the PDK version, and a reviewer promotes it through the lifecycle to the published catalog.
• Propose policies as ideas when you want one but haven't built it yet, and vote on what other people have proposed.
• Deploy approved policies into your own Anypoint organisation through a Connected App, in either a DEV (Publish) or stable (Release) mode, without managing any deployment pipelines yourself.
• Collaborate with teammates inside shared workspaces that group members, Anypoint connections, and live deployments under role-based access (Owner / Admin / Member).

This page covers signing in and finding your way around. The other guides in this section walk you through each of those flows in detail.

Sign in to P4A

Open the portal sign-in page at /login. P4A supports three sign-in methods — pick whichever you prefer; they all land you in the same account, keyed off your email address.

• Email and password — enter the email and password you registered with. If you don't have an account yet, follow the Register link from the sign-in screen to create one.
• Continue with Google — single sign-on through your Google account. The first time you use it, Google asks for permission to share your email and name with P4A.
• Continue with GitHub — single sign-on through your GitHub account, with the same first-time consent step.

The two OAuth buttons (Google and GitHub) live below the email/password form. Choose any method on any visit — for example, you can register with email/password and later sign in via Google as long as the Google account uses the same email address.

When you sign in with Google or GitHub for the first time, P4A automatically creates a profile for you using the name and email returned by the provider — there's no separate registration step. With email and password, you create the profile yourself by following the Register link before your first sign-in. Either way, you can update your display name and company label later from the Profile modal in the sidebar.

Dashboard tour

Once signed in, the dashboard is your home base. If this is your first time signing in, a guided tour automatically launches — it walks you through the main navigation, the resources group, and each of the key sections listed below. You can follow the step-by-step overlay, dismiss it and explore on your own, or replay it later from Take the tour in the profile menu at the bottom-left. The sections below describe the same areas in detail.

Policies

Browse all published policies at Policies (/dashboard/policies). Filter by category, search by name, and view details before deciding to deploy a policy.

The page has two tabs. Community (the default) is the catalog of policies built and submitted by the community — the ones you can deploy into your own Anypoint organisation. MuleSoft is a read-only reference list of the out-of-the-box policies that ship with the MuleSoft Omni Gateway; each one opens an in-portal detail page with its full documentation and a link out to the official docs. Use the MuleSoft tab to check whether MuleSoft already ships a policy for what you need before building or deploying a custom one.

Ideas

Propose and vote on policies you'd like to see at Ideas (/dashboard/ideas). This is where the community upvotes policy requests and where contributors can find ideas to implement (see Submitting an idea).

Each policy's detail page carries a Report an issue action next to View source. It opens a pre-filled bug report on the policy's own GitHub repository — where the author tracks issues — so you can flag a problem without leaving the portal. You add a one-line summary in P4A, then finish and submit the report on GitHub under your own account. The action is hidden for policies whose repository has its issue tracker turned off.

Workspaces

At /dashboard/workspaces, see your personal and shared workspaces, switch the active workspace, and manage members. Every account has a personal workspace by default, and you can also belong to one or more shared workspaces; each membership carries a role — Owner, Admin, or Member — that determines what you can do inside it. For a deeper walkthrough see Using workspaces.

Anypoint Connections

At /dashboard/connections, manage Anypoint Connected App credentials. Each connection belongs to a user and can be linked into a shared workspace so teammates can deploy through it. See Deploying a policy for how connections are used end-to-end.

My Contributions

At /dashboard/submissions, track policies and ideas you've submitted, from draft through review to published. Monitor lifecycle state changes and review feedback. See Lifecycle states under Submitting a policy for what each state means.

Transfers

At /dashboard/transfers, review ownership transfers — offers to take over a policy someone else owns, and offers you've made to others. When someone offers you a policy, a count badge appears on the Transfers item in the sidebar. See Transferring policy ownership for the full flow.

Profile

Click the avatar at the bottom-left of the sidebar to open a small menu with Profile and Sign out. Choosing Profile opens a dialog where you can update your company label — the free-text label that appears next to your name on policies and ideas you submit. Full name and email come from your sign-up (provider account for Google / GitHub, registration form for email and password) and aren't editable here — contact support if you need to change them. The Roles field lists any platform roles you've been granted (most users see just User).

Email notifications

The same Profile dialog has an Email notifications section where you can mute the transactional emails P4A sends you. New users start with everything turned on — toggling a category off stops only the emails you opt out of, the rest keep flowing. The available categories are:

• Policy submission updates — under-review, needs-improvement, rejected, and published emails for your own policy submissions.
• Policy idea updates — approved, needs-improvement, and rejected emails for your own ideas.
• Reviewer invitations — emails sent when an admin invites you to review a policy currently under review.
• Ownership transfers — emails when someone offers to transfer a policy to you, or when a transfer you started is accepted or declined.
• Workspace membership — emails sent when you're added to or removed from a shared workspace, or when your role in it changes.
• Workspace updates — emails sent to every member when a shared workspace you belong to is renamed or otherwise updated.
• New policy submissions (admin) — admin-only alert on every new policy submission. Visible only to platform admins.
• New policy ideas (admin) — admin-only alert on every new idea. Visible only to platform admins.

Changes take effect on the next event — there is no batching or digest mode. Preference changes are recorded in the platform audit log so admins can trace them.

Signing out

The same avatar menu has a Sign out entry. Choosing it ends your session immediately and returns you to the sign-in page; the next visit to any dashboard URL will redirect you to /login.