Symptom

Users assigned the Admin role may find themselves unable to access or utilize Launch features within their instance. This prevents high-level users from managing projects or configurations.

Root Cause

Access to Launch is governed by instance-specific keys. If the Launch key for a specific instance is not enabled, the feature remains inaccessible regardless of the user's assigned role.

Resolution

Enable the Launch key for the affected instance. This restores visibility and functionality for all users with appropriate roles within that instance.

Verification

The issue is resolved when users with Admin roles can successfully view and interact with the Launch dashboard and its associated tools.

Symptom

Accessing Contentstack Launch may appear restricted when a user is uncertain if permissions are enabled. This prevents users from beginning work within the Launch interface until access status is confirmed.

Root Cause

The user already had the required permissions and active access to the Launch environment, so no technical remediation was necessary.

Resolution

1. Navigate to the Launch login page and attempt to sign in with your credentials.
2. Verify that there are no authentication or permission error messages displayed during login.
3. Check your user profile settings to ensure the Launch feature is visible in your organization.
4. Confirm that you can access and view your projects within the Launch dashboard.

Verification

After completing the resolution steps, log in to the Launch interface and open a project. If you can successfully view the dashboard and interact with your projects, the issue is resolved.

Symptom

Unable to locate the administrative settings required to permanently remove a project from the Contentstack Launch dashboard. This prevents the cleanup of unused or test environments and may lead to a cluttered project list.

Root Cause

The project deletion option is located within the project-specific settings and requires explicit confirmation, which can make it difficult for users to identify without specific guidance.

Resolution

1. Log in to your Contentstack account and click the Launch icon from the App Switcher.
2. From the Launch landing page, select the specific project you wish to delete.
3. Click the Settings icon from the top panel or left navigation menu.
4. In the General section, scroll down to the Delete Project area.
5. Click the Delete Project button.
6. In the confirmation modal that appears, type DELETE in the input field.
7. Click the Yes, Delete button to permanently remove the project.

NoteThis action is irreversible and will remove all domains and environments associated with the project.

Verification

After completing the deletion steps, return to the Launch main dashboard. If the deleted project no longer appears in your project list and all associated URLs are inactive, the issue is resolved.

Symptom

Attempts to create a new environment via the Launch Command Line Interface (CLI) fail because the functionality is currently restricted. This limitation requires an alternative workflow to establish new environments before they can be managed via terminal commands.

Root Cause

Creating new environments is currently a UI-only feature in Launch. While CLI support for this action is on the product roadmap, it is not supported in the current version of the tool.

Resolution

1. Manually create the new environment through the Launch user interface.
2. Once the environment is established in the UI, use the Launch CLI for subsequent tasks such as deployments and configuration management.
3. Monitor official release notes for updates regarding expanded CLI capabilities for environment creation.

Verification

After manual creation in the UI, use the Launch CLI to list or manage the environment. The issue is resolved when the CLI successfully recognizes and interacts with the newly created environment.

Symptom

Launch remains inaccessible within a Contentstack instance despite an active subscription, preventing the creation of new projects or environments.

Root Cause

Access to Launch is dependent on the completion of the provisioning process. This process is managed by a separate team (CSM/Provisioning) and falls outside the scope of technical support. Access may be paused if required administrative documentation or paperwork is outstanding.

Resolution

Ensure that all required administrative documentation and service agreements have been completed and submitted. Technical support cannot provision Launch; the request must be finalized by the Provisioning or Customer Success team once the paperwork is processed.

Verification

Attempt to access the Launch application from the App Selector. The issue is resolved when the Launch dashboard loads successfully and permits the creation of new projects.