Adding new functions to restrict user access to the database/table

[maximmensah]

Adding new functions to restrict user access to the database/table

Recently, I have realized the need for new functions to restrict users in NocoDB, and so I started this discussion to explore some of these possibilities.

I have seen someone bring up this issue recently, but I don't think they fully covered the topic limit the options.. #5284 My desire is to be able to limit users who have been added to a project, such as an editor, by giving them access to only selected columns (not necessarily, but it would be great).

In addition to this, I have identified some more serious issues:

1. The existing function in the table that allows the maximum number of characters to be limited for text columns does not work.
2. I cannot limit an attachment column based on the required attachment type, so users currently have the ability to upload any type of file to the column, rather than what is necessary. For example, the column should strictly contain photos with extensions webp, jpg, jpeg, or png, but the user accidentally or intentionally uploads a file with a larger size.
3. There is no way to limit the maximum number of attachments in a column, so the user can upload more attachments than necessary, which slows down NocoDB and its API when processing requests and displaying data in NocoDB - this is something I have already encountered.
4. When I used Airtable, I had a limit of 1200 records for the entire database on the free plan. I would really like this limit to exist in NocoDB as well, but in a more expanded form, and for users with Owner privileges to be able to limit the Editor from adding records to each table. For example, the editor has access to two tables (Products and Categories), and in the Products table, the user can add a maximum of 1100 records, while in the Categories table, a maximum of 100 records. After 1100 or 100 records, the Add Record button disappears, and the editor cannot exceed this limit in any way.
5. The project as a whole needs to limit the use of disk space among all users. For example, this is directly related to the aforementioned points 2 and 3.