Thanks @DMehaffy,
for the second, perfect that was exactly what I was looking for!
The third though seems like it’s not possible to hide the fields, since I want the people with a role having the rights to change the field to see it, and I can’t have role based views so it’s either going to say “forbidden” for authors and be visible for editors, or it’s going to be hidden for both?
Just an example to hopefully make it clearer as I’m not sure I’m explaining myself well:
A user with the role Author creates a post. The posts have subject, text, ready for publishing, tags and qa state. I want authors to fill out subject and text. Then when they are done they set ready for publishing.
Then an Editor picks it up, proof reads the text and the subject, adds tags which makes sense and set the qa state to validated and then publishes the article.
In this case I’d like tags and qa state hidden for the author, they are irrelevant for them and not allowed to edit them. But I do want the editor to see them, as far as I understand that means those two fields have to be visible and say “not allowed”? What I’d like is if a field is not allowed, then don’t show it because it’s just confusing clutter for the author.
Like I said, it’s not the end of the world but like with other hidden fields (created_by, …) it feels saner to just not show disallowed fields.