no permission to see this field in strapi

Question

I am unable to enter data to fields which I have created in user collection type in strapi.

I wanted to create extra fields in user collection in strapi so I created some extra fields from builder , but when trying to enter data , the newly created fields are not editable .

Developing

I got this "no permissions to see this field" after exporting some json at Settings -> Interface for a field that I had just added. The fun part is that I had access to that field minutes before - I could edit it. I fixed this by restarting the server (was not enough) and then doing log out and then log in. A bit weird. – Fingerstall

For me restarting the server solved the issue! – Honeycutt

Answer 1

This issue generally occurs when new fields are added to existing content types.

In my case, Simply signing out and logging in back in with your Admin account solves the issue. This will reset the permission issue for newly created fields.

Hummer

This worked nicely. – All

Answer 2

You can try following ways, and check if any one of them works -

Method 1

there can always be an issue with Strapi server,

• I restarted the server manually and it is fixed.

Method 2

your user might not have permission to view that field. you can change permission of a user by -

step 1 - Login to your strapi cms with Admin account and check if you are able to edit that field(the one with no permission), if so then continue with following steps, else this method wont work for you.

setp 2 - click on settings in left panel , select the user , from the list select the user that you want to change permission with, give read write , and other permissions you want to give.

re-login with your account from which you were facing the problem, it should work now

Method 3

There might be a sync issue with your DB, sometimes your data is not synced with your DB, try deleting the field and re creating it.

I hope one of this solves your issue

Developing

Method 3 worked for me with Strapi 4.5.6 - I only changed a field name of a collection content type and re-deployed to heroku -> works. – Overestimate

Answer 3

After I ran into the issue multiple times myself and couldn't fix it even after re-deploying again (and again...), I found the following worked for me:

• In the deployed version, go to Content-Type Builder
• Select the content type that contains the field causing problems
• Click the Configure the view button
• Change the position of an arbitrary field
• Click Save

This worked for me and also didn't require a re-deployment of my app.

Overestimate

Answer 4

I got this issue after updating to the 3.6.11 version. Try to remove .cache and build folders and rebuild the app. This worked for me.

Electromechanical

Answer 5

After none of the solutions describe here worked for me I found a "quick" way to fix this.

1. Open the corresponding schema.json of your affected collection:

-src
  |-api
     |- <singularName of collection>
        |- content-types
           |- service
              |- schema.json

2. Add temporally "required": true, to the field under attributes:

{
  "kind": "collectionType",
  "collectionName": "xxx",
  "info": {
    "singularName": "xxx",
    "pluralName": "xxxs",
    "displayName": "XXX",
    "description": ""
  },
  "options": {
    "draftAndPublish": true
  },
  "pluginOptions": {},
  "attributes": {
    /* [...] */
    "yourFieldName": {
      "type": "relation",
      "required": true, // <== ADD HERE!
      "relation": "manyToMany",
      "target": "api::yyy.yyy",
      "inversedBy": "zzz"
    },
    /* [...] */
  }
}

3. If the field is a relation (manyToMany) open the corresponding collection and repeat the step above for this collection.
4. Run strapi in development mode: npm run develop (depending on your command defined in package.json.)
5. Stop the development mode.
6. Revert back your changes in schema.json files.
7. Run and stop strapi in development mode again.

This should fix the broken entry in the database. From now on the field should be visible.

Brayer

Additional info: This workaround is compatible with Strapi version 4.25.6 – Brayer