Help center
Open dashboard

Introducing the New Atarim WordPress Plugin: Everything You Need to Know

Install it, connect it, and control who collaborates — plus what version 5.0 lets Atarim’s AI actually do on your site.

Atarim team Updated 30 Jul 2026 · 12 min read
Integrations
The Atarim WordPress plugin connected, with its capabilities listed
Before you start

Relevant for

  • Agencies, developers and site owners who want feedback and AI collaboration to happen on the WordPress site itself — including staging sites that are not publicly reachable.

Required knowledge

  • Comfortable installing a WordPress plugin and reaching WordPress admin settings.

Tools & resources needed

  • WordPress 5.0 or later.
  • PHP 7.4 or later.
  • An Atarim account and administrator access to the site.

The Atarim WordPress plugin brings visual collaboration onto the site itself, rather than onto a fetched copy of it. That is what makes it the right choice for staging environments and any site that is not publicly reachable — and version 5.0 adds a defined set of actions Atarim’s AI can carry out on the site directly.

Plugin settings live in WordPress admin, separate from your Atarim dashboard.

The plugin is listed in WordPress as Atarim – Visual Feedback, Review & AI Collaboration, and the current release is version 5.0. It brings visual collaboration onto the site itself — which is what makes it the right choice for staging environments and any site that is not publicly accessible.

Check your PHP version first
The plugin requires PHP 7.4 or later and WordPress 5.0 or later. An outdated PHP version is the most common reason an install fails or the plugin activates but does nothing, and the resulting error rarely names the real cause.

What the Plugin Enables

Installing the plugin changes where collaboration happens. Instead of reviewing a copy of the page, you and your team work on the site itself — which unlocks a set of things a shared link cannot do.

What you getWhy it matters
Works on staging and protected sitesBecause collaboration runs on the site, it reaches environments that are not publicly accessible.
Visual feedback on live pagesComments attach to the element they are about, so nobody has to describe where they mean.
AI review of any pageRun a review to identify gaps before a client sees the page rather than after.
Internal tasks hidden from clientsWork you do not want reviewed sits in the same project without appearing in the client’s view.
Private internal notesTeam-only discussion lives on the task, invisible to clients and silent on notifications.
Client-friendly feedbackMark review findings internal and clients see their own thread rather than your quality notes.
Clients need no WordPress accountGuest Mode or ?collab=true lets them ask questions in place.
Note
Internal tasks and private notes are visible to administrators and team members only. Clients and guests never see either, and private notes do not trigger notification email. Explore Internal Tasks

Install from the WordPress Plugin Repository

The fastest route if you have not downloaded the plugin from your Atarim dashboard.

  • In your WordPress admin panel, go to Plugins → Add New.
  • Search for Atarim.
  • Select Install Now on the correct plugin. Look for Atarim – Visual Feedback, Review & AI Collaboration so you install the right one.
  • Activate the plugin when the option appears.
  • The Plugins Add New screen in WordPress admin
    Go to Plugins → Add Plugin in your WordPress admin panel
    Searching for Atarim in the WordPress plugin directory
    Search for Atarim
    The Install Now button on the Atarim plugin listing
    Select Install Now — check the name reads Visual Feedback, Review & AI Collaboration
    Activating the Atarim plugin after installation in WordPress
    Activate the plugin when the option appears

    Or Download It from Your Atarim Dashboard

  • Log in to your Atarim workspace.
  • Go to Projects if you are not already there.
  • Select Add Snippet.
  • Choose Install WordPress Plugin. The plugin download becomes available as a .zip file.
  • The Projects screen in the Atarim dashboard
    Start from Projects in your Atarim workspace & Click Add Website
    The Add Snippet control on the Atarim Projects screen
    Download the Plugin
    Choosing Install WordPress Plugin from the Add Snippet options
    Choose Install WordPress Plugin
    The Atarim plugin downloading as a zip file
    The plugin downloads as a .zip file. Install and activate it in WordPress.

    Installing the Downloaded File

  • Go to your WordPress dashboard.
  • Navigate to Plugins → Add New Plugin.
  • Select Upload Plugin, choose the .zip file, and select Install Now.
  • Activate the plugin.
  • The Add New Plugin screen in WordPress admin
    In WordPress, go to Plugins → Add New Plugin → Upload Plugin
    Uploading the Atarim plugin zip file in WordPress
    Select Upload Plugin, choose the .zip, then Install Now
    Activating the uploaded Atarim plugin in WordPress
    Activate the plugin

    Connect the Plugin to Your Atarim Account

  • After activation you are taken to the Atarim settings screen in WordPress.
  • Select Connect with Atarim. You are redirected to your Atarim dashboard to complete the connection.
  • After activating the plugin, the Connect WordPress to Atarim screen appears with your site’s address already filled in. Select Connect site to link it to your Atarim account.
    The Atarim settings screen in WordPress shown after activation
    You are redirected to your dashboard to complete the connection
    The Connect with Atarim button on the plugin settings screen
    Confirmation screen reading “You’re connected”
    The Atarim dashboard completing the plugin connection
    Connected WordPress site with the Atarim overlay open
    Note
    If the redirect does not happen, refresh the settings page and select the button again.

    The Settings Screen

    Plugin settings live in WordPress admin, under Settings → Collaborate.

    SettingWhat it does
    DisconnectDisconnects the site from your Atarim dashboard. This stops all collaboration features on the site and removes it from your workspace.
    Project SettingsOpens project-level configuration without leaving WordPress.
    ShareCopy the collaboration link, invite clients or team members, and manage access from the settings page.
    Guest ModeLets people leave feedback without a WordPress account. You can also add ?collab=true to any URL to activate guest access on that page.
    Who can collaborateSelects which WordPress user roles see the collaboration interface when logged in. Only the selected roles see it unless Guest Mode is on.
    AutoLoginNominates a WordPress user account for one-click access. When you select Collaborate in Atarim, that user is signed in automatically.
    Save & ApplyStores your changes. Nothing takes effect until you select it.
    The Collaborate settings screen in WordPress admin
    Settings → Collaborate, in WordPress admin rather than the Atarim dashboard
    Project settings and collaboration options opened from the WordPress plugin
    Project Settings opens without leaving WordPress
    Choose an AutoLogin user with enough permission to collaborate
    Typically an administrator or editor. Nominating an account without the right capabilities produces a login that succeeds but a session that cannot do anything. Learn More About User Roles And Permissions
    Tip
    Appending ?collab=true to a URL is the most useful sharing route day to day — it opens collaboration on one specific page without changing any settings or generating a new link. Explore URL Collaboration

    Sharing from the Settings Screen

    The Share control opens the same sharing options you would use in Atarim — copy the collaboration link, invite clients, or add team members — without leaving WordPress.

    Open sharing options to invite clients and collaborators
    The Atarim sharing panel opened from WordPress, with options to add team members and copy a link
    Add team members, invite clients, or copy a collaboration link from here

    How WordPress Users Start Collaborating

    A WordPress user whose role is allowed in the settings sees a collaboration launcher in the WordPress sidebar.

  • The user selects the Atarim launcher from the sidebar.
  • A consent modal appears.
  • They select Connect your WordPress account to proceed. They are connected to the project and can collaborate immediately, and are added to the project as a collaborator.
  • The Atarim collaboration launcher in the WordPress sidebar
    The launcher appears for roles selected under Who can collaborate
    The consent modal asking a WordPress user to connect their account to Atarim
    The consent modal — accepting joins them as a collaborator
    Consent adds them as a collaborator, not a team member
    Every WordPress user who gives consent joins as a collaborator by default. For someone to be a team member — with dashboard access, project visibility and role permissions — they must be invited to your Atarim account first. Use the same email address for a person in both WordPress and Atarim: matching accounts mean that once they give consent they are recognised as a team member with no extra steps, and it avoids a whole class of permission confusion later.

    Collaborating with Your Team and AI on a Page

    The collaboration panel on a page includes Chat for internal team members, so a team can work through a page together and bring AI into the same conversation. From there you can discuss page-level changes, run internal AI reviews, check the page across desktop, tablet and mobile, and leave feedback on a single element or the whole page. AI works with the full page context — layout, spacing, copy, visuals and structure.

    Chat comes from Atarim, not the plugin
    It is an Atarim surface the plugin makes available on your site rather than a feature of the plugin itself. If Chat is not behaving as expected, it is not a plugin problem — check your Atarim account and connection first.
    Mark AI review findings internal before you share the page
    Internal tasks are hidden from clients and guests entirely, which is what stops a quality pass reading as a list of faults in front of the client. Explore Internal Tasks

    Collaborating Inside WP Admin

    Collaboration is not limited to front-end pages — it also works on WP Admin screens. That is useful for leaving internal reminders, flagging settings that should not be changed, and coordinating backend implementation work. Feedback left in WP Admin can be marked internal in the same way.

    Atarim collaboration running on a WP Admin screen
    Collaboration works on WP Admin screens too, not just front-end pages
    Note
    Like Chat, WP Admin collaboration comes from Atarim’s collaboration interface rather than the plugin’s own settings, so there is nothing to switch on for it in Settings → Collaborate.

    What “Do It” Can Do on the Site

    Two things are easy to confuse here, so it is worth separating them before the capability list.

    A preview shows you what a change would look like. When a suggestion is offered on an element, you can preview it and the change appears on screen straight away — then disappears again. Nothing is saved, nothing reaches your database, and it exists only in that person’s browser for that moment. It answers “did you mean this?” visually instead of in words, which is why it works so well with clients who cannot quite describe what they want. Previews cover wording changes on a single text element and look changes such as size, colour, weight, spacing and alignment.

    “Do it” makes the change for real. It works through the capabilities below, writing to the actual WordPress site — content, media, themes, settings and the rest. It is authenticated by the site’s connection token and is not visible to clients or guests.

    Preview is reversible, “Do it” is not
    A preview reverses because nothing ever happened. A completed action is a real change to your site, and the way back is a backup. Treat the two with different levels of caution — preview freely, and think before you run an action on production.

    Version 5.0 exposes a defined set of capabilities on the site, grouped by area. Knowing what is in scope tells you what to expect — and what to be careful about.

    AreaCovers
    ContentPosts, pages and the content within them.
    Gutenberg and blocksBlock editing and block navigation.
    Patterns and templatesReusable patterns and site templates.
    MediaThe media library.
    Metadata and taxonomiesPost metadata, categories and tags.
    Themes, theme files and global stylesTheme-level changes, including site-wide styling.
    PluginsPlugin-level operations on the site.
    UsersWordPress user accounts.
    SettingsWordPress site settings.
    CacheClearing caches after a change.
    A preview of a suggested change rendered on a page element
    Enable Do It option
    The Do it action carrying out a real change on the WordPress site
    “Do it” writes the change
    This reaches beyond post content
    The capabilities include theme files, plugins, users and site settings. Take a backup before letting AI actions run on production, and try them on staging first. The plugin makes the change; it does not second-guess whether you wanted it.
    Note
    The “Do it” AI action is not visible to clients and guests, so it can stay available without a client triggering a change to the site.
    Tip
    Plugin installation is one of the actions in that list, and it installs whichever plugin it is asked to. If you have a standard plugin you use for caching, SEO or forms, record those preferences in The Stack so the choice is decided once rather than per site. Discover The Stack

    How the Connection Is Secured

    When the site is connected, a secret token is generated and stored on it. Every request Atarim makes carries that token in a header, and the plugin checks it before acting.

    Two consequences follow. The connection is tied to the token rather than to a WordPress user account, so it is not affected by someone’s WordPress login. And disconnecting and reconnecting establishes a new token, so anything relying on the old one stops working until the reconnection completes.

    The capabilities described above are exposed through a server the plugin runs on your site, which Atarim calls to carry out an action. That server is what the token protects, and it is why the connection state matters as much as the plugin being active.

    Note
    This is separate from connecting external coding agents to Atarim, which uses Atarim’s own endpoint rather than one on your site. If you are setting up Claude or Codex, that is the Atarim MCP article.

    Example Use Cases

    SituationHow the plugin helps
    A staging site behind a passwordCollaborate on the site directly, where a shared public link cannot reach.
    A quality pass before a client reviewRun an AI review, then mark the findings internal so the client sees only their own feedback.
    A client who keeps emailing questionsGive them guest access so questions land on the page they are about.
    Onboarding a new client to a projectShare the collaboration link from the settings screen without leaving WordPress.
    A developer joining mid-projectAdd their WordPress role to Who can collaborate so they see the interface when logged in.
    Frequent trips into the dashboardOpen Project Settings from inside WordPress instead.
    Repeated logins when collaboratingNominate an AutoLogin user so Collaborate signs you straight in.

    Known Limitations

  • PHP 7.4 and WordPress 5.0 are minimums. Older stacks are not supported.
  • Plugin settings are separate from Atarim settings. The role picker and AutoLogin live in WordPress admin.
  • Settings need Save & Apply. Nothing takes effect until you select it.
  • Consent creates collaborators, not team members. Team membership requires an Atarim invitation.
  • Reconnecting issues a new token, so the previous one stops working.
  • AI actions reach beyond content — including themes, plugins, users and settings.
  • FAQs

    What is the plugin called in WordPress?

    Atarim – Visual Feedback, Review & AI Collaboration. The current release is version 5.0.

    What are the minimum requirements?

    WordPress 5.0 or later and PHP 7.4 or later.

    Can I collaborate on staging or protected sites?

    Yes. Because the plugin runs on the site itself, it works where a publicly reachable link would not.

    Can clients leave feedback without a WordPress account?

    Yes, with Guest Mode enabled, or by adding ?collab=true to the page URL.

    Can clients trigger AI actions?

    No. “Do it” is not visible to clients and guests.

    What happens if I disconnect the site?

    Collaboration features stop on that site and it is removed from your Atarim workspace.

    Will tasks created in WordPress appear in the Atarim dashboard?

    Yes. The plugin is a way into the same project, so tasks created on the site show up in that project’s views in your dashboard.

    Does the plugin replace the Atarim dashboard?

    No. It brings collaboration onto the site and puts some project settings within reach, but the dashboard remains where projects, boards and workspace settings live.

    What happens if I uninstall the plugin?

    Collaboration features stop working on that site. Tasks already created stay in your Atarim project — removing the plugin does not delete feedback you have collected.

    How does Atarim authenticate to my site?

    Through a secret token established at connection, sent with every request and checked by the plugin.

    Common issues

    • The plugin will not install or activate — check the site runs PHP 7.4 or later and WordPress 5.0 or later.
    • No collaboration interface after activation — confirm the site is connected, and that your WordPress role is selected under Who can collaborate.
    • A colleague cannot see the launcher — their role is not selected in the settings, or Guest Mode is off and they are not logged in.
    • Settings changes had no effect — select Save & Apply. The screen does not autosave.
    • Someone joined as a collaborator instead of a team member — invite them to your Atarim account first, using the same email address as their WordPress account.
    • AutoLogin signs in but nothing works — the nominated account lacks the permissions to collaborate. Choose an administrator or editor.
    • Atarim cannot reach the site after reconnecting — a new token was issued. Complete the reconnection so both ends match.
    • An AI action changed more than expected — restore from backup and run future actions on staging first.
    • The site is behind a firewall and will not connect — whitelist Atarim at the host or WAF level. See the whitelisting guide.

    Conclusion

    Installation is straightforward: install from the repository or upload the file from your dashboard, connect, then set who can collaborate. The settings worth deliberate thought are the role picker and AutoLogin, because both decide who can act on the site.

    Version 5.0 also gives Atarim’s AI a defined set of actions it can perform — reaching content, media, themes, plugins, users and settings. Set it up the way you would set up anything with that reach: backup first, staging before production.

    Tips & best practices

    • Confirm PHP 7.4 or later before installing.
    • Use matching email addresses in WordPress and Atarim so consent recognises team members.
    • Keep Who can collaborate limited to roles that should have it.
    • Pick an AutoLogin user with enough permission to actually collaborate.
    • Use ?collab=true to open collaboration on one page without changing settings.
    • Back up before letting AI actions run on production, and try them on staging.
    • Remember to select Save & Apply.

    Related articles