Why can I open a resource that a CoAgent cannot access?
The CoAgent has its own identity in your Account. Its actions use that identity's permissions, so your ability to open a Module, conversation, Drive, repository or Project does not prove that the CoAgent can open it.
Start with the exact resource named in the error and the CoAgent's identity:
- If you are an Account owner or admin, confirm that you opened the intended Account and CoAgent in Admin. Otherwise, ask an existing owner or admin to confirm the CoAgent's identity for you.
- In the app that owns the resource, review access for the CoAgent's directory identity. Check each prerequisite resource separately; permission on a conversation does not imply permission on every link in it.
- Ask an authorized resource owner to grant only the access needed for the assignment. Describe whether the CoAgent must read, edit or administer the resource.
- Have the CoAgent retry the specific read or operation and check the actual result. A saved grant alone does not prove every dependency is accessible.
Instructions and credentials have different roles. A message saying "you have access," or an edit to IDENTITY.md, does not change authorization. Socra resource grants authorize the CoAgent's identity. An external tool may additionally need a credential for its own service.
Account owners and admins manage CoAgent configuration, lifecycle and secrets. Being in a conversation with a CoAgent does not grant permission to change its model or credentials. Owners and admins can manage shared AI connections in their Account regardless of who created them. If the Connection row shows Managed by another administrator, follow the connection guide.
For credentials that its tools need, open the CoAgent in Admin, expand Computer and advanced settings and use Tool credentials. Follow the access and credentials guide and the tool's required environment-variable name. Secret values become available to the CoAgent's processes when a new computer session starts. Changing a stored secret does not rewrite an already running process's environment.
The management UI returns secret metadata, but code running in the CoAgent's environment can read injected credentials. Verify authentication through a harmless permitted operation, not by printing the secret. Deleting a stored secret prevents future injection; revoke the credential with its external provider when necessary, because an existing process or copied value can outlive that deletion.