Prismic is a content management system. Where we can easily manage our content, we can add, remove, update and create new fields for our content. It is an API based CMS so it is easy to configure our programming language or framework. It enables front-end developers to build websites and apps using any technology, programming language or framework: React, Angular, Node, Vanilla JS/PHP/Ruby etc.
How to use :
Sign Up, Log In, and Log Out
This page explains how to create a Prismic account and how to log in to Prismic.
The log in and sign up page
To get started, go to the Log In or Sign Up page.
A link to the “Log In / Sign Up” page is always accessible to logged-out users in the top-right corner of the homepage.
You can choose to sign up using your email or your GitHub account.
With your email
Click the option Sign up with my email. Then, enter your information and click Create Account. You should now be logged in.
Please remember your password and keep it secure.
This option enables single sign-on authentication. It applies your GitHub credentials each time you login to your Prismic account.
On the “Log In / Sign Up” page, login using the same method you used to signup, using your email or your GitHub account.
With your email
Select Log in with my email. Enter your email address and password and click Log In.
Select Log in with GitHub. Enter your GitHub credentials and click Sign in.
If you’re already logged in to your GitHub account, the Log in with GitHub button will automatically take you to your Dashboard.
Please note: If you have previously used your email to signup to Prismic and it is the same email you use on Github, you cannot directly connect your Github account.
If you’ve forgotten your password, visit this link and enter your email address:
To log out, navigate to the Prismic dashboard:
Then, click the on/off icon in the top-right corner of the screen:
What Is a Repo?
In Prismic, your repo stores all of the content for a project. It contains all of the documents, media, environments, translations, and settings for your project. Prismic hosts this content in the cloud for you, and you can edit it via the Prismic platform.
Prismic is priced by repo, starting at a fully functional free tier, with higher tiers for additional users and features.
Accessing a repo
You can view all of your repositories and create new ones in your dashboard:
Each repo has its own URL, with this format:
To open your repo, navigate to this URL. If you’re not logged in, you will be prompted to do so.
Your Prismic repo is only accessible to Prismic users who have been invited to the repo. Learn more about user roles.
Your repo is only accessible to users who have been given access. However, your repo has an API endpoint that exposes your repo’s content as JSON data. This API can be set to public or private.
What a repo does
In your repo, you can:
- Add and remove users
- Change your subscription plan
- Create Custom Types, which are models for your content
- Add and edit documents
- Add and edit media
- Plan content releases
- Add webhooks
- Manage settings for the repo
On the left-hand side of your repo, you will see five or six buttons, depending on your permissions:
- The first button with the Prismic logo will tag you to your dashboard.
- The second button will take you to the document screen, where you can browse, create, and edit content.
- The third button will take you to your Custom Types, where you can model content. This button is only visible to administrators.
- The fourth button, the image, will take you to your Media Library.
- The fifth button, the question mark, will take you to the Prismic documentation.
- The sixth button, the cog, will take you to your repo settings.
Deleting a repo
Deleting a repo is irreversible. Once a repo is deleted, there is no way to get it back.
In the settings for your repo, navigate to Danger Zone in the menu.
Click Delete the repository.
You will be prompted to type in the name of the repo and your password. Then, click Delete this repository.
Your repository is now deleted.
Starting on the Starter plan, you can invite users to your repo. To invite a new user, go to Settings > Users. In the input field, type in the new user’s email address and click “send.”
The new user will receive an email notification and if they don’t already have a Prismic account, an invitation to sign up.
The new user will appear as Pending until they have accepted their invitation. A pending invitation is counted as one user in your plan.
You can cancel an invite by clicking Cancel in the pending invitations list.
In Basic plans, all users have the role of Administrator.
In Professional plans, there are three user roles available: Writer, Publisher, and Administrator.
Once a user has accepted an invite, you can set their role. All new users have the role of Writer by default.
User roles facilitate a collaborative workflow. Here are the rights and abilities of the different roles:
– Create draft documents
– Edit documents, without publishing changes
Everything a Writer can do, plus:
– Review and publish drafts and edits
– Schedule publications
Everything a Publisher can do, plus:
– Edit repo settings
– Create and edit Custom Types
There is only one Repository Owner
Everything an Administrator can do, plus:
– Access and edit billing information
These user roles are designed to allow Writers to create content and Publishers to review and publish content.
Warning: Payment details
When you transfer ownership of a repo, any payment details will remain. That means you might continue to get billed for the repo after you have been removed from it. Consider deleting payment details before transferring ownership.
In Settings > User, there is a section for transferring ownership of your repo to another user.
Select the user you want to transfer ownership to, and click Transfer ownership.
Free plans can only have one user, so this feature works differently.
Because free plans can only have one user, transferring ownership means that you will lose access to your repo.
In Settings > Users, scroll to Transfer ownership. Type in the email address of the new owner, and then click Transfer ownership.
The ownership will transfer when the new owner accepts the ownership. Until that point, you can cancel the transfer by clicking Cancel.
Roles per Locale
Roles per locale gives you more control over user roles in multi-language repositories.
Roles per locale is available on Enterprise plans
Reach out to our Sales team for more information.
To user roles per locale, you must have at least two locales in your repository. Learn how to add locales in Manage Languages and Locales.
Configure the roles per locale
Only Administrators can edit user roles. Let’s go over the steps for inviting users and editing their roles.
Note about feature activation
When Roles per Locale is activated for the first time, anyone who wasn’t already an administrator will be able to view documents in all languages but without access to edit them. You’ll need to assign each member their new roles per locale to enable them to edit.
In your repo, go to Settings > Users. Send an invitation to a new user. You can grant or limit access to certain locales from the moment you send the invitation.
Edit user roles
Go to your repository’s Settings > Users. Select the languages for each user using the + Add a locale button.
By default, everyone in the repository can see all documents in all existing locales, but they will only edit for the locales you give them access to.
The Roles per Locale facilitates a collaborative translation workflow. Once you grant a specific role to a user, you can assign their role per locale. There are two main user roles: Contributors and Admins.
Once you grant the contributor role to a user, you can assign their role for each locale. Their role can be either Writer or Publisher.
- Create draft documents.
- Edit documents without publishing changes.
- View documents from other locales and copy them to permitted locales.
Publishers can do everything a Writer can do, plus:
- Review and publish drafts and edits.
- Schedule releases if they have publisher rights for every locale in the release.
Administrators can do everything a Contributor can do, plus:
- Access all locales.
- Modify user roles and permissions.
For more information about standard user roles, consult Manage Users.