Is Staff, Is Superuser, groups

[amitu]

We do not have these two fields, and I propose we add them to fastn_user table. We probably should also add group. We should also add permission table. And basically follow the django model for all these. Permissions can be assigned to users or groups.

The earlier group we discussed, we can stop calling them group, and call them "attribute" or something, eg anyone who has this attribute can do this, and the attribute is a computed thing (which may call external services). Computed attributes can be cached etc.

[amitu]

We are thinking of adding a lot of "intranet" features to FifthTry, which are only accessible to employees, so is-staff is needed, and some of them can only be given to admin (eg to add staff status to someone).

Ideally these should be done using CR tho, so we can easily track things, and people can propose things etc. I guess we have to evaluate on save do db update stuff, which can help with all this.

[amitu]

Or maybe we have "managed table", like a processor that manages a table. It can either manage the entire table, or it manages a single row.

In FASTN.ftd. We will keep the hash of name-of-table and if it changes we will re-create the table with the data.

-- fastn.managed-table: name-of-table

CREATE table name-of-table(
    name TEXT NOT NULL,
);

-- fastn.csv:

;; body is CSV

;; either `fastn.csv` or `fastn.row` should be used. 

-- fastn.row: <primary key>
name: value ;; data



-- end: fastn.managed-table

We can put the managed row in a document also. So eg a blog meta data can be handled via managed-rows.

-- fastn.managed-row: <primary key>
table: <table name>
column: value

Of course this needs on save update feature. But we have to only worry about managed-row for now.