--- title: "Access Groups, better template editing, Railway Agent Connectors" date: 2026-08-14T10:53:00.000Z number: 0303 url: https://railway.com/changelog/2026-08-14-access-groups --- # Access Groups, better template editing, Railway Agent Connectors The best infrastructure changes are reviewable, reversible, and visible to the right people. This week, Access Groups bring project-level controls to Enterprise workspaces, templates gain Agent-assisted editing with staged review and rollback, and Railway Agent Connectors bring external tools into the conversation. Let's get into it! πŸš„ # Access Groups beta [Configure project access](https://cms.railway.com/media/access-groups.mp4) Enterprise workspaces no longer have to choose between giving every member access to every project and managing access one person at a time. Access Groups let workspace admins group people, assign a project role, and attach that group to any set of projects. Create and manage groups from **Workspace settings β†’ People β†’ Groups**, then see the resulting direct and group-derived access under **Project settings β†’ Members**. You can configure groups before enforcement is enabled. Workspace admins turn enforcement on under **Workspace settings β†’ People β†’ Security**, after reviewing which people would lose access and which projects would have no remaining non-admin access. Once enabled, non-admin members see only projects granted through an access group, direct project access, or a project they created. Workspace admins retain access to every project. Access Groups are available on eligible committed spend plans. Check out the [Access Groups documentation](https://docs.railway.com/enterprise/access-groups), and share your feedback on [Central Station](https://station.railway.com/new?type=feedback). # Better template editing Template editing now has a review and recovery loop. Changes stage before they reach the template, applied versions appear in **Activity**, and [Railway Agent](https://docs.railway.com/ai/railway-agent) can propose edits from the same editor. ## Review staged changes before applying them [Templates staged changes](https://cms.railway.com/media/staged-changes-templates.mp4) [Staged changes](https://docs.railway.com/deployments/staged-changes) for templates are generally available. Edits to services, variables, networking, and template metadata land in a single change set. Review the complete diff, then apply the changes together or discard them. Previously, the template editor saved changes directly. Related edits landed one at a time, without a single diff to review before updating the template. Each applied change set appears in **Activity** with a record of what changed. Open the current Activity entry to undo that change set, or select an older entry to stage a revert to that version. Reverts return to the staged review flow before you apply them. Previously, template authors had no built-in history for inspecting and restoring earlier versions. ## Edit templates with Railway Agent [Use Railway Agent to create and edit templates](https://cms.railway.com/media/railway-agent-templates.mp4) Click **Agent** inside the template editor and describe the reusable stack you want. Railway Agent can create, update, and remove services, functions, and buckets. It can add Railway's official Postgres, MySQL, MongoDB, and Redis templates, configure variables, networking, and metadata, and check variable references and publishing guidelines. Agent edits use the same staged workflow, so you review the proposed diff before applying or discarding it. You can enable **Template Editor Chat** under [Feature Flags](https://railway.com/account/feature-flags). Try the new template workflow, and let us know what you think on [Central Station](https://station.railway.com/new?type=feedback). # Railway Agent Connectors beta [Bring external tools into Railway Agent chats.](https://cms.railway.com/media/agent-connectors.mp4) Railway Agent Connectors are available in beta! To get started, enable **Railway Agent Connectors** under [Feature Flags](https://railway.com/account/feature-flags). Connect Notion, Linear, or Sentry through OAuth, or register a custom remote MCP server. The agent can search Notion pages and databases, read Linear issues, projects, and cycles, pull Sentry issues and stack traces, and use tools exposed by your own MCP servers. Navigate to **Workspace settings β†’ Agents** and configure your connectors, then attach them to an agent chat from the **Contexts** picker. Each connector belongs to the person who creates it. Its tools are available only to that person’s agent runs, and credentials stay private. Checkout the [Railway Agent Connectors documentation](http://docs.railway.com/ai/agent-connectors) to configure Notion, Linear, Sentry, or a custom MCP server and attach it to a Railway Agent chat. Context makes agents better, and feedback makes betas better. Share yours on [Central Station](https://station.railway.com/new?type=feedback). # Fixes and improvements - We shipped a way to restore a bucket during its pending-deletion window. Previously, pending bucket deletions could not be cancelled from the dashboard. - We fixed rare cases where structured logs appeared without message text even though their attributes were present. - We fixed deployment history pagination when skipped deployments are hidden. Previously, a page filled with skipped deployments could leave the history looking incomplete and prevent older deployments from loading.