Michael Bridgen a39e7edd1b Explain authorisation model and mechanisms ... The multi-tenancy implementations described rely on impersonation and remote apply; to make this RFC stand by itself, those need to be explained, along with the authorisation model (how Flux "decides" what it's allowed to do). This commit adds a summary of the authorisation model, impersonation, and remote apply, and rejigs the headings a little to make space. Signed-off-by: Michael Bridgen <michael@weave.works>		2021-12-09 14:10:25 +00:00
..
0001-multi-tenancy	Explain authorisation model and mechanisms	2021-12-09 14:10:25 +00:00