GraphCMS focuses on the benefits and how we can help you get better results for your business or your customers. This focus on use to the user is what makes GraphCMS unique.
Shabnam M. Content Specialist
I is a good and lovely CMS that in addition to Flexibility to customizing schemas, Stunning GraphQL API with powerful query and mutation facilities. My overall experience with GraphCMS Excellent customer support.
Ali K.Information Technology Adviser
We are building heavily for mobile devices, so using GraphQL for our content APIs is really helping our app performance. Our developers also love the code autocomplete function and the self-generated API documentation in the API Explorer. Quite intuitive UI for business users."" Markus H. CEO"
Very powerful GraphQL capabilities and the new UX is on point.
Permanent Auth Tokens
For most applications, you'll want to use a Permanent Auth Tokens. This allows you to grant individual API keys restricted access to your projects content. Permanent Auth Tokens are also really useful if you later want to revoke access to any content.
A typical use case for Permanent Auth Tokens is occurs when working with content stages. When content editors save drafts, or publish to various stages, API keys can be scoped to deliver content from those stages.
Your development team may wish to use a Permanent Auth Token that is scoped to **DRAFT** content only — this way they know they can create new content entries with test data without worrying it'll go live on the website.
Content editors may wish to have a separate staging environment they can preview new articles, and website content changes before they go live. If you were using a custom content stage for QA, your staging website could be scoped to only fetch from this content stage.
Once content lands in the **PUBLISHED** content stage, your production website would be scoped to fetch only production ready content thanks to the Permanent Auth Token rules.