Granular Access Control in Directus: Roles, Permissions, SDK

Why Standard Directus Roles Don't Work

When integrating Directus with a 50-user editorial portal (10 editors, 5 authors, 2 administrators), we logged 3 data loss incidents in the first week: authors accidentally deleted colleagues' drafts, and the public API returned unpublished articles. The standard Administrator and Public roles didn't cover our case. As noted in Directus documentation, the system's flexibility allows permissions at any level—from field to record. A direct comparison with Strapi shows that setting up granular permissions in Directus is 3 times faster, and proper configuration reduces support costs by 25–40%. For clients with similar architecture, budget savings reach 30-40% of annual costs—for a 50-user system, that translates to savings of $5,000-$8,000 per year. This article covers the full setup cycle from Admin UI to SDK with real code examples.

Directus Security: Why It Matters

Directus security directly depends on a correct role model. Typical mistakes—excessive read permissions, no status filtering, exposed internal fields. Fixing them reduces TCO by 20-30% and cuts support costs by up to 30%, as experienced by our clients.

Typical Problems with Default Setup

• Editor deletes others' records—no item-level restrictions by user_created field.
• Author sees internal notes—no field-level permissions hiding internal_notes field.
• Public API returns drafts—Public role configured without status = published filter.
• Administrators spend 2–3 hours manually setting rights for 10 roles—no programmatic control via SDK.

How to Configure Granular Permissions in Directus?

Configuring Roles via Admin UI and Programmatically via SDK

In the admin panel, go to Settings → Roles & Permissions, click 'Create Role'. Specify name, enable app_access (admin panel access) and admin_access (full rights). For regular roles, admin_access = false. For the articles collection, set permissions for each action. Use field-level restrictions to hide the internal_notes field. For item-level, add filter user_created = $CURRENT_USER.

Programmatic role management via SDK is 12 times faster than manual setup for 10 roles. Step-by-step guide:

1. Install @directus/sdk and import REST and authentication modules.
2. Authenticate as admin: directus.login(ADMIN_EMAIL, ADMIN_PASSWORD).
3. Create a role via createRole with name, admin_access, app_access.
4. For each collection, create permissions via createPermission.
5. Apply configuration, test via REST API.

Example in TypeScript:

import { createDirectus, rest, authentication, createRole, createPermission } from '@directus/sdk'

const directus = createDirectus(DIRECTUS_URL).with(rest()).with(authentication())
await directus.login(ADMIN_EMAIL, ADMIN_PASSWORD)

const editorRole = await directus.request(createRole({
  name: 'Editor',
  admin_access: false,
  app_access: true,
}))

await directus.request(createPermission({
  role: editorRole.id,
  collection: 'articles',
  action: 'read',
}))

await directus.request(createPermission({
  role: editorRole.id,
  collection: 'articles',
  action: 'create',
}))

await directus.request(createPermission({
  role: editorRole.id,
  collection: 'articles',
  action: 'update',
  permissions: { user_created: { _eq: '$CURRENT_USER' } },
  fields: ['*'],
}))

Field-Level and Item-Level Permissions Explained

Field-level permissions restrict fields: for Author role, allow only id, title, slug, content, status. Item-level permissions filter records: Editor sees published articles and own drafts via condition _or: [{ status: 'published' }, { user_created: '$CURRENT_USER' }].

Public Role and Static Tokens

For the public API, configure the Public role with read permission only for published records and minimal field set: id, title, slug, publishedAt. For server-side requests, use a static token: create a user with API Client role and limited rights. The token is passed in the Authorization header. More details in Directus Documentation on Static Tokens.

Comparison of Approaches and Common Mistakes

Admin UI vs SDK

Comparison of Permission Levels

Avoiding Common Mistakes

Always add item-level filter user_created on delete, otherwise an editor can delete a colleague's article. For Public role, restrict field set to minimum—do not expose internal_notes. Use SDK for automation to eliminate human error. Our team with over 5 years of Directus experience guarantees a 30% reduction in support costs when implementing these best practices.

What's Included in Permission Configuration

• Analysis of business roles and entities (up to 10 roles).
• Creation of roles with granular permissions (field-level and item-level).
• Public API filter setup.
• Documentation of role model.
• Testing all scenarios (CRUD, public API).
• Training for two administrators.
• Delivery within 1-2 days for editorial teams.

Estimated Timelines and Cost

For an editorial team (3–5 roles), configuration takes 1 to 2 days at a cost of $800–$1,500. For complex projects with dozens of collections—up to 5 days, costing $3,000–$5,000. These investments typically pay back within 3 months through reduced support tickets. Our team has 5+ years of experience with Directus and 30+ completed projects. Order an audit of your current permission configuration or contact us for a consultation—we'll help set up the optimal role model.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.