Access problems usually come from the permission matrix, tag state, account status, or misunderstanding which audience a visitor belongs to. Start by checking whether the user is public, signed in, or the owner.

Other people cannot see the profile

• Open the Access page and check whether the intended audience has permission to view the profile.
• If visitors are not signed in, they count as public visitors and need public profile access.
• If the profile is limited to signed-in users, visitors must log in before they can view it.
• Check the tag state. A disabled tag may not behave like an active public tag.
• Make sure access changes were saved. Unsaved permission changes do not affect the public tag page.

Visitors cannot create entries

• Check whether the intended audience has permission to create entries.
• The tag needs an active schema before entries can be created.
• Public visitors need public create-entry permission if they should create entries without signing in.
• Signed-in users need authenticated create-entry permission unless public create-entry permission already allows it.
• Check whether the tag is active. Disabled tags should be reactivated before normal entry creation is expected.

Users cannot view entries

• Check whether the user’s audience has permission to view all entries.
• If users may only view their own entries, they will not see entries created by other users.
• Public visitors need public entry-view permission if entries should be visible without signing in.
• Signed-in non-owner users follow authenticated permissions plus any public permissions that also apply to them.
• The owner should still be able to view owner-allowed entry content from the owner dashboard.

Users cannot edit or delete entries

• Check whether users are allowed to edit or delete their own entries.
• Editing or deleting all entries is more powerful and should usually be limited to the owner.
• If a user only has own-entry permission, the entry must belong to that user.
• Anonymous entry editing may depend on the stored local edit token for that entry.
• Be careful with public edit or delete behavior. Public write access should only be enabled when it is really intended.

Public users have more access than expected

• Public permissions apply without signing in and also apply to signed-in users.
• If public visitors can do something, signed-in non-owner users can usually do it too because public access is the broadest audience.
• Reduce public permissions first when access is broader than expected.
• Keep sensitive actions such as managing access, schema, profile, and state owner-only.

Access changes did not apply

• Check whether the Access page still shows unsaved changes. If so, save the access settings.
• If you used Revert, the page returned to the last saved permission matrix.
• Reload the public tag page after saving access changes.
• Test with the correct audience. A signed-in owner may see more than a public visitor.
• If behavior still looks old, open the tag in a private browser window to test the public visitor experience.