Pages Improvements: Permission for record creator

[PatrickRQ]

Hello,

Pages already providers pretty nice solution of managing fields permissions. However, an extra permission would be very useful, visibility of field for topic creator only and staff of course.

Often while designing some app, like e.g. bug tracker there is a need of creating a private reports, visible to report creator and staff only. Such extra permission would allow us to decide whether some fields within a new record can be seen by everybody or to topic creator and staff only.

Please consider that feature for nearest pages update.

[opentype]

1 hour ago, PatrickRQ said:

Often while designing some app, like e.g. bug tracker there is a need of creating a private reports, visible to report creator and staff only. Such extra permission would allow us to decide whether some fields within a new record can be seen by everybody or to topic creator and staff only.

That kind of exists already. If you set the database to “new records must be approved” it behaves this way. The user’s records will only be visible to themselves and staff. Unless they are approved, which shows them to everyone who has read permissions. 

[PatrickRQ]

@opentype, thanks for pointing that out.

Yes, that would be kind of similar functionality. However it will force a need to approve all records before they appear. Considering "private" records are just small % of all other reports it should work reverse way to avoid inconvenience of constant approving new records. This is also not the system admin who should decide whether to submit private record, just the submitter. This is why extra permission would be handy.

I also suggested an ability to set this kind of permission to selected fields only, so record itself may be visible to all but selected fields visible to record creator and staff only. Currently it is only possible to set field visibility per entire member group.

[opentype]

8 minutes ago, PatrickRQ said:

I also suggested an ability to set this kind of permission to selected fields only, so record itself may be visible to all but selected fields visible to record creator and staff only. Currently it is only possible to set field visibility per entire member group.

Hu? What the first sentence describes is certainly possible already – based on member groups. Not sure why you say it is limited to “entire member group”. What else should it be based on?

If you have special requirements, like giving record creators the change to hide stuff, that is better solved through template customizations. I can’t see how IPS would make fundamental changes to how fields work just to serve niche cases.