# Fix sign-in, permission, and saving problems

Identify whether a failure comes from the session, team role, plan, or form fields.

## You cannot sign in

Use **Forgot Password** from the sign-in screen, then follow the reset email. Complete email verification if prompted. An invitation must be accepted by the intended account; ask an owner or admin for a fresh invitation if the link is invalid.

## A team or action is missing

Check the team switcher and selected project. Owners and admins manage organization settings and projects; users can edit ordinary project work; viewers have narrower access. An owner or admin can review your membership in **Settings → Users**.

Plan availability is a separate check. For example, comments and lifecycle customization are not included on Free, Solo, or Freelance, and MCP is unavailable on Free.

## Changes fail to save

1. Keep the unsaved content available while reading the error.
2. Check the highlighted fields and required relationships.
3. Verify that selected pages, metrics, or other linked records belong to the correct project.
4. If the app reports read-only mode, ask the billing administrator to resolve the subscription state.
5. If your session has expired, sign in again and check the record before repeating the change.

Survey **Build** and **Settings** have separate save actions. A preview change is not a saved change until the corresponding save completes.

## Uploads fail

The browser attachment picker accepts images up to 5 MB; use JPEG, PNG, or GIF for formats accepted throughout the upload flow. Organization logos have a 2 MB image limit, and changing an existing project cover has a 1 MB server limit. The REST attachment API separately supports image and document formats up to 10 MB. Use the specific field's validation message when an upload is rejected.

## Ask for help with useful context

Choose **Copy support context** below the article, then **Open feedback portal** and paste the article details into your request. Describe the action attempted, a redacted error message, and the approximate time. Keep the request suitable for a public feedback post: omit API tokens, integration credentials, private team records, and unredacted response data.