# Project access and connection problems Generated: 2026-11-13T08:01:29.316Z Source build: local Canonical docs: https://teammately.ai/docs --- id: workflow.troubleshooting.access-and-connections title: Project access and connection problems summary: You cannot open a Project, contribution, source, or connected workflow. kind: error product_area: troubleshooting status: stable updated: 2026-11-11 canonical: /docs/troubleshooting/access-and-connections --- # Project access and connection problems ## Symptom You cannot open a Project, contribution, source, or connected workflow. ## Likely causes | What you observe | Focused guide | | --- | --- | | The workspace reports an IP access restriction | [IP access restriction](/docs/troubleshooting/authentication) | | The object or operation is unavailable to your account | [Permissions troubleshooting](/docs/troubleshooting/permissions) | | An intake connection or captured batch needs diagnosis | [Fieldloop Intake and Processing](/docs/troubleshooting/fieldloop) | ## Fix Confirm the workspace, Project, signed-in identity, and actual restriction shown. Inspect grants and connection state through their existing administration surfaces. Preserve the difference between a workspace network restriction, missing Project access, and a provider connection problem. Follow the focused guide for the actual state you observe; keep accepted records and explicit human decisions intact. ## Prevention Preserve exact object and version identities, review the relevant source context, and inspect the accepted state before comparing outcomes. ## Related task pages {% related-card-grid title="Return to the workflow" %} - [Complete your first alignment loop](/docs/quickstart) {% /related-card-grid %} ## Related reference pages {% related-card-grid title="Diagnose the observed state" %} - [IP access restriction](/docs/troubleshooting/authentication) - [Permissions troubleshooting](/docs/troubleshooting/permissions) - [Fieldloop Intake and Processing](/docs/troubleshooting/fieldloop) {% /related-card-grid %} --- id: troubleshooting.authentication title: IP access restriction summary: Resolve the current Access Restricted page when the detected IP is not on the Workspace allowlist. kind: error product_area: troubleshooting status: stable updated: 2026-11-11 canonical: /docs/troubleshooting/authentication --- # IP access restriction Use this when Teammately displays **Access Restricted** and says the current IP is not on the Workspace allowlist. Sign-in, Project membership, and Contribution assignment are separate problems. ## Symptom The page reports **Access restricted by IP** and shows a detected client-header IP, backend-detected IP, or both. ## Likely causes - The current IPv4 or IPv6 address is not on the Workspace allowlist. - A VPN, proxy, gateway, or network change caused the detected address to differ from the expected address. - The client-header and backend-detected addresses differ, so the administrator needs the value actually shown by the product. ## Diagnostic checks - Read both detected IP values shown on the page. - Confirm whether the user recently changed networks or enabled a VPN. - Copy the displayed address instead of relying on an address from another device or external lookup. - If the page no longer appears but Project content is still unavailable, continue with permissions troubleshooting. ## Fix - Send the displayed IP to the Workspace administrator. - Have the administrator add the required single address or CIDR in the applicable security settings. - Retry after the allowlist change is active. If the detected address changed again, resolve the network or VPN source before adding more entries. ## Prevention - Confirm the expected access network before time-sensitive Contributions or evaluations. - Prefer a stable organizational network path when the Workspace uses IP restrictions. - Keep IP restriction, Project membership, and Contribution assignment diagnoses separate. ## Related task pages {% related-card-grid title="Related task pages" %} - [Request an Expert Contribution](/docs/expert-contributions/request-contribution) - [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution) - [Complete your first alignment loop](/docs/quickstart) {% /related-card-grid %} ## Related reference pages {% related-card-grid title="Related reference pages" %} - [Permissions](/docs/reference/permissions) - [Reviewer and Project Access](/docs/governance/reviewer-and-project-access) - [Workspaces, projects, and target systems](/docs/object-model/workspaces-projects-and-target-systems) {% /related-card-grid %} --- id: troubleshooting.permissions title: Permissions troubleshooting summary: Separate Project membership from Expert Contribution assignment and readiness when an expert has no tasks available. kind: error product_area: troubleshooting status: stable updated: 2026-11-06 canonical: /docs/troubleshooting/permissions --- # Permissions troubleshooting Use this when project role, reviewer assignment, or approval ownership prevents someone from completing the intended work. ## Symptom A user can access Teammately but cannot open the expected Project, or an expert reports **no tasks available** after opening their Contribution link. These symptoms belong to different owning surfaces. ## Likely causes - The user lacks the required Project permission through a direct grant, workspace group, or workspace role. - The Contribution was requested for a different recipient. - The Contribution exists but its next Task or Checkpoint is not ready. - The current IP is blocked before Project membership is evaluated. ## Diagnostic checks - Check direct grants in **Project Settings → Project Members**, the user's workspace-group membership, and the group's permission for the intended Project. Absence from the direct member list alone does not establish lack of access. Inspect workspace status and role in **Admin → Directory → Members** as well. - Open the Contribution from the sender-side Expert Contributions workspace and verify its recipient and status. - Check whether the expert has an executable Task or Checkpoint, not merely whether the Contribution exists. - If **Access Restricted** is visible, resolve the IP allowlist first. ## Fix - Add the correct individual workspace user under **Project Settings → Project Members** when direct Project membership is missing. - If access is intended through a workspace group, confirm both the user's membership in that group and its permission for the intended Project. - Correct the Contribution recipient through the owning Contribution workflow when the request went to the wrong person. - Resolve lifecycle or readiness problems in Expert Contributions when access succeeds but no Task can be entered. - Do not infer a permission from a role label or edit governed artifacts merely to make a control appear. ## Prevention - Separate reviewer access from approval authority in review setup. - Check assignments before launching a review session. - Use a small pilot Contribution before assigning a larger specialist cohort. - Keep project membership changes visible to review owners. ## Related task pages {% related-card-grid title="Related task pages" %} - [Request an Expert Contribution](/docs/expert-contributions/request-contribution) - [Expert Contributions](/docs/expert-contributions) - [Complete an Expert Contribution](/docs/expert-contributions/complete-contribution) {% /related-card-grid %} ## Related reference pages {% related-card-grid title="Related reference pages" %} - [Permissions](/docs/reference/permissions) - [Roles and Permissions](/docs/governance/roles-and-permissions) - [Expert Contributions](/docs/expert-contributions) {% /related-card-grid %} --- id: troubleshooting.fieldloop title: Fieldloop Intake and Processing summary: Resolve source, destination, intake, processing, and Thread issues while preserving captured records. kind: error product_area: troubleshooting status: stable updated: 2026-11-06 canonical: /docs/troubleshooting/fieldloop --- # Fieldloop Intake and Processing ## Symptom A submission has no expected log, a batch reports rejected or conflicting rows, processing is waiting, or captured records have not produced an expected Thread. ## Likely causes - The credential, Project or source destination does not match. - The original submitter's receipt is being read from another principal. - A retry changed content while keeping the same idempotency identity. - Intake is admitted but row processing is not complete. - Source processing consent is absent or revoked. - Provider capacity or a recorded processing failure delayed analysis. - The selected records do not support an inquiry. ## Fix Inspect the original receipt and its row counts first. Confirm the workspace, Project, source and original logical request. Retry an uncertain submission only with its exact content and key. Read Logs for captured content and processing state. Check the source's current permission and the reported error through the normal controls. Keep accepted records and their provenance intact. A missing Thread is not automatically an intake failure. Analysis may legitimately publish no inquiry. Do not invent a report, change source facts or broaden provider access to force a visible result. If a typed input-coverage discovery was published, inspect its related Inbox item separately. Report publication, Case generation and dataset adoption have different outcomes. ## Prevention Retain original source records until admission is known. Keep credentials in the host secret mechanism, preserve exact retry identity and monitor row outcomes rather than HTTP success alone. Configure source permission deliberately. Revoke processing through its owning control when needed; do not treat an access change as authorization to rewrite published history. ## Related task pages {% related-card-grid title="Related task pages" %} - [Fieldloop](/docs/fieldloop) - [Capture and Inspect Logs](/docs/fieldloop/ingest-logs) - [Read Fieldloop Threads](/docs/fieldloop/threads) {% /related-card-grid %} ## Related reference pages {% related-card-grid title="Related reference pages" %} - [API Keys and Delegated Access](/docs/admin-console/api-keys) - [Input Coverage Inbox](/docs/coverage-design/inbox) {% /related-card-grid %}