Skip to content

Unauthorized users can be trainers #104

@nwf

Description

@nwf

It is, at present, possible for a user to not be authorized on a piece of equipment and yet be a trainer. I'm not sure who and what, but apparently there's at least one such instance in the database right now. It'd be nice to make this state slightly harder to get into, even if we don't rule it out completely (by, say, making trainer status imply authorized status).

Quoting @azend from Slack for reference:

Yeah. You’re right. It isn’t a bug per se but it is ux awkwardness. I think creating implicit authorization may not be the best approach. But we can look into auto add auth on addition of trainer/steward or a change of ui to force creation of authorization before adding additional responsibilities.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions