← Back to all sparks
T

Tines

DEVOPS
Velocity5.0

No-code workflow automation and orchestration platform for security and IT teams

Tines lets admins grant each product area separately without splitting teams.

security automationpermissionsai governancerecordsenterprise controls
◆Current state
Tines is a security-automation platform whose recent releases split between Records and Cases as a structured data layer and governance controls around Apps and AI. The November 13 release lets admins grant access to each product area independently, so analysts and builders on the same team can see different parts of the platform. It follows tenant-wide fallback models and a multi-path Condition action earlier in the month.
◆Where it's heading
Records has gained new field types, a v2 read API, and write access through the Tines MCP server, turning it into a system of record that AI clients can edit. The admin track keeps getting finer: SSO-group app restrictions, keyless cloud credentials, tenant model fallbacks and now per-product permissions all move control below the team level.
◆Prediction
The next likely step is per-team or per-story AI model policies, extending tenant-level defaults the way permissions just moved below the team. A write-side Records API v2 to match the September read endpoints also fits the pattern.

◆Recent moves

  1. 15h ago

    More granular control over product access

    Admins can now grant access to each Tines product area separately while users stay on the same team. It is another step in the enterprise-controls track, after SSO-group app limits and tenant model defaults.

    View source ↗
  2. 1d ago

    Condition actions now support multiple paths

    One Condition action can now route events down up to 10 ordered paths, replacing chains of separate Conditions. It is a builder-quality change that makes large stories easier to read, in line with the platform's recent focus on maintainability over new surfaces.

    View source ↗
  3. 11d ago

    Set default fallback models for your whole tenant

    Tenant owners can now set default smart and fast models with an ordered list of up to five fallbacks. It is a reliability control for AI steps in stories, consistent with Tines adding admin-level governance rather than new AI capabilities.

    View source ↗
  4. 29d ago

    Keyless cloud credentials with workload identity federation

    AWS, Google Cloud, Entra, and Oracle Cloud credentials can authenticate via workload identity federation, removing long-lived keys from the tenant. For a security-automation vendor, this closes an obvious credential-hygiene gap and fits the enterprise-controls track.

    View source ↗
  5. 1mo ago

    Full-text search and filter groups in Cases

    Cases search and filtering were rebuilt with full-text search and filter groups. It makes Cases more usable as a working queue as volume grows, matching the parallel investment in Records.

    View source ↗
  6. 1mo ago

    Create, update, and delete Records via the Tines MCP

    AI clients connected to the Tines MCP server can now create, update, and delete records and record types. Moving MCP from read-only to write access makes Records a data layer that external agents can maintain directly.

    View source ↗