Multi-Factor Authentication (2FA) & Security

Stack invitations cannot be accepted when login credentials for the platform have not yet been established. Access to the specific stack is not granted until login credentials for the platform have been established.

Root cause

Organization-level access and valid login credentials must be established before a user can accept invitations to individual stacks.

Resolution

1. Obtain organization-level access to the platform.
2. Log in through Okta.
3. Accept the stack invitation once organization access is confirmed.

After obtaining organization access and logging in, check the stack list to verify if access is restored.

Attempting to access Contentstack may fail during the login process.

Root cause

The user account is not associated with any organization, preventing access to the platform.

Resolution

1. Request an organization invitation from the relevant administrator.
2. Accept the invitation to join the organization.
3. Attempt to log in to Contentstack.

If the user successfully accesses the platform after joining the organization, the issue is resolved.

Accessing a demo organization may result in visibility issues when the organization does not appear in the dashboard and access emails are missing.

Root cause

The user lacks formal ownership or an accepted invitation for the specific organization, preventing it from appearing in the user interface.

Resolution

1. Contact Contentstack Support to request an organization ownership transfer email.
2. Accept the ownership transfer invitation.

After accepting the ownership transfer, verify the visibility of the organization in the dropdown menu. If the organization appears as expected, the issue is resolved.

Attempting to access entries within an organization may result in the dashboard failing to load and displaying a "Something went wrong" error.

Root cause

Role-related inconsistencies in user permissions prevent the dashboard from syncing and loading correctly.

Resolution

1. Contact the organization owner or administrator to refresh account permissions.
2. Change the organization role from Member to Admin, then revert it to the original role (or vice versa if currently an Admin).
3. Remove the user from the organization and re-add them with the correct role to resync access.

After re-adding the user and updating roles, attempt to access the organization entries. If the dashboard loads without error, the issue is resolved.

Logging in to Lytics or resetting account passwords may fail when using the standard login page or credentials.

Root cause

The account requires authentication through a specific OAuth link rather than the standard login process.

Resolution

1. Request the manual OAuth login link from Contentstack Support.
2. Use the OAuth link instead of the standard login page to log in to Lytics.

After using the OAuth link, attempt to authenticate. If the login is successful, the issue is resolved.

Stack access may be restricted and roles may be unassignable when SSO or Identity Provider management is enabled for an organization.

Root cause

When SSO/IdP is enabled and managed externally, user roles and stack permissions must be synchronized through the Identity Provider rather than being manually updated within the Contentstack platform.

Resolution

1. Verify the user is already part of the organization and has accepted the organization-level invitation.
2. Coordinate with the internal IdP team to assign the appropriate roles and permissions via IdP groups for the required stack.
3. Ensure the internal team creates and maps the necessary groups in the IdP for new stacks.
4. Test stack access after the user has been assigned to the correct IdP groups.

After the IdP team updates the group assignments, attempt to access the specific stack in Contentstack. If the user can see the stack and perform actions aligned with their assigned role, the issue is resolved.