Understand access and solve common problems

A project or ticket is not available

First check the selected workspace. Then check whether you have access to the project and its team. A private project may not appear in navigation or search until its manager grants you access.

A ticket link in chat does not grant access. If a reference says Ticket not available or Project not available, ask the appropriate manager to check your current access. The same applies to issue mentions, search results and files attached to restricted work.

1. 1

   Confirm the context

   Check the workspace selector and the project or team you intended to open.

2. 2

   Request specific access

   Tell the manager which project and type of work you need. Request read access if you only need to inspect it, or edit access if you are responsible for changes.

3. 3

   Refresh after an access change

   Reload the work after the manager updates access. Your integration connection also follows current permissions.

I can read a page, but cannot change it

Read access and edit access are different. A disabled create, edit or configuration action can reflect your role. Team settings, project membership changes and credential creation can require management permission.

Ask a manager to make the change or grant the required access. Selecting multiple issues, pasting a direct URL or using an AI connection does not bypass the permission check.

Sign-in or account setup is blocked

Check that you are using the current account email, not just the display name on your profile. A changed sign-in email or expired session can require a fresh login. A temporary password, first-time profile setup or authenticator challenge must be completed before entering the workspace.

• Use the password visibility icon to check a mistyped password.
• Ask your administrator for a fresh one-time reset link if necessary.
• Finish the welcome profile setup, including the detected timezone.
• If you have no active workspace, ask for an invitation to the correct workspace.
• Do not share an invitation token, password or authenticator code in a support message.

A save or upload failed

Read the error before retrying. The record may have changed, a required field may be missing, your permission may have changed, or the connection may be interrupted. An error is not confirmation that the requested change was saved.

1. 1

   Protect unsaved work

   Copy the draft text before refreshing if you need to preserve it.

2. 2

   Check the current record

   Refresh the page and inspect whether the change is present. If another person edited the ticket, read the current version before applying your update.

3. 3

   Check uploads separately

   Look at the upload queue for the file’s final status. Check its format, destination permissions, storage allowance and the upload error before retrying.

4. 4

   Retry the specific action

   Retry only after you know what remains unsaved. This reduces duplicate tickets, comments and files.

Send a useful support request

Describe what you were trying to do, the page and workspace context, the visible message, and the steps needed to reproduce it. Include a screenshot only after checking that it contains no private keys, passwords or information you are not permitted to share.

Your workspace manager is the best first contact for project membership and roles. For product questions, use Suparko’s public Contact page. Include the request or reference ID if an error displays one.