User Accounts - Login
You can sign on to Quintype using the username and password that your administrator has created for you. Alternatively, you can sign on using your social accounts such as Google, Facebook, Twitter or LinkedIn.
To Login to your account:
- Open the link provided by your administrator.
- Enter the username and password provided by your administrator and click Login.
- Or Click on one of the social media icons and authorize your account.
The Workspace panel is displayed, depending on the homepage setting.
Troubleshooting Login Issues
If you are unable to sign on, try one of the following methods:
- If “No” roles are assigned. Contact an admin!” error message is displayed, contact your administrator. The administrator must add the required permission for your account.
- If the "Authentication failed ” error message is displayed, either try re-entering your password or click Forgot password? Clicking on Forgot password sends an email to your login ID to reset the password.
User Accounts - Assign Or Remove Roles **
An administrator can assign or remove roles from an account. To assign or remove a role:
- From the main menu, select Settings > Users and Roles.
- Select the user and disable the login
- To assign a role, select from the email address, assign roles and save.
User Accounts - Roles And Permissions
In the Quintype environment, specific Permissions allow you to perform specific tasks. One or more permissions are clustered together to define a Role. Roles are then assigned to the Account IDs of users.
Permissions are of three types: Content, Analytics, and Admin.
- Content permissions are relevant to managing content in your stories. Story save, publish and retract, edit options etc.
- Analytics permissions allow you access to the analytics page and the download reports.
- Admin permissions are relevant to user creation and role management; they also include Tag related permissions.
Once a role is defined, that role can be assigned to one or more users. Permissions are what allow users to perform their day-to-day tasks in the system. Any member who has ‘admin’ level access can assign roles to other users. Each role can be customized to allow or restrict permissions on the story editing interface. For example, a ‘Guest Contributor’ role can have access to create stories and submit for review to an ‘Editor’. An ‘Editor’ role can have the authority to reject or publish the story.
A Role inherits permissions from its Parent Role. You can assign additional permissions to that role, but you cannot disinherit permissions received from the parent role.
Here is a list of permissions and what each means:
|Permission Name||What it Means|
|access-all-content||See Notifications from everyone|
|access-analytics||Ability to access analytics|
|access-comment-manager||Ability to access comment manager|
|access-entity-manager||Access entity manager option|
|access-tag-manager||Ability to access tag manager|
|admin||Access to Admin Dashboard and everything there.|
|breaking-news-save||Save and publish breaking news|
|collection-edit||Edit a collections|
|collection-read||View only access for collections|
|entity-delete||Ability to delete entities|
|entity-save||Ability to create and save entities|
|set-assignments||Assign someone else as an author|
|share-filter||Ability to share a filter created on workspace|
|story-approve||Approve a story|
|story-close||Close a live blog|
|story-delete||Delete story from workspace|
|story-publish||Publish a story|
|story-reject||Reject a story|
|story-retract||Retract a story|
|story-save||Save a story. This permission is also required to access editor.|
|story-schedule||Schedule a story|
|story-schedule-cancel||Cancel a scheduled publish|
|story-schedule-modify||Modify a schedule publish|
|story-social-media-check||Show social share on a story|
|story-sort||Sort a story|
|story-submit||Submit a story|
|tag-create||Create a tag|
|tag-delete||Delete a tag|
|tag-edit||Edit a tag|
|story-public-preview||Ability to access a public preview URL for a story|
|collection-rank-nested-collection||Ability to rank collections within a collection|
Bold Release Notes: 30 January 2020:
Single sign on into all your websites
Quintype's upgraded user authentication service is now equipped to handle a single-sign-on of users into your suite of websites on the Quintype platform.
Get in touch with us at [email protected] to configure it or write to our sales team at [email protected]
Bold Release Note - 1 May 2020:
Quintype's Independent Auth Service
Quintype's Independent Authentication service is now live. Built for robustness and scale, the feature rich application in its first go-live includes all APIs typically required for an authentication service, and is listed here.
Several important bug fixes such as cursor jumping and keyboard shortcuts such as Ctrl+a(Cmd+a in mac), Ctrl+v(Cmd+v) etc are fixed.
Bold Release Note - 8 Sep 2020:
Two Factor Authentication in Quintype authentication service
Quintype's independent user authentication service now has the Two Factor Authentication capability for added security to your applications.
Contact [email protected] or [email protected] to know more.
Bold Release Note - 29 Dec 2020:
Two-factor-authentication on Bold
Bold is now equipped with the ability to require two-factor-authentication to login to Bold. Once enabled for your publisher account, all users will have to scan the QR code on subsequent login or go to My Profile and setup the login using any TFA app like Google Authenticator app, Authy, etc. Once it is setup for the user, every login will require the user to enter a 6 digit code from the TFA app to login to Bold.
The Admin can turn on the feature at: Settings > Configure > Features > Two Factor Authentication.
Bold Release Note - 29 Dec 2021
Automatic Single Sign-On (Auto SSO)
Quintype's Auth service now allows automatically detecting and signing in of users on multiple websites of a publisher. Auto-Single Sign-On using Quintype Authentication Service documentation is available here:
Apple OAuth login on mobile apps
Quintype's Authentication service now has a new flow for Apple login Mobile implementation.
Documentation is available here: