{% extends "layouts/settings.html" %}
{% comment %}
The team, in the shape contacts/tag_list.html established — but three lists on
one page rather than one, so each gets its own .section-title over its own card.
The invite form's field names are untouched: apps/members/views.py parses
`ws_` and `ws_role_` by exact string, so the per-workspace pairs have to
keep spelling themselves that way however they are laid out.
Changing somebody's role is an inline reveal off the "…" rather than a select
sitting in every row. A dropdown that silently posts on change, on a control that
can demote the person reading it, is not a thing to leave lying in a list.
{% endcomment %}
{% load common_extras %}
{% block title %}Team members · DemandTrail Messaging{% endblock %}
{% block content_wrap %}{% endblock %}
{% block content %}
Team members
Everybody in this organization, what they can do across it, and which workspaces they
can reach.
{% comment %}
Asked first (HANDOFF §2.4): they lose access at once, and only
a new invitation brings them back. Alpine's @submit, because
the CSP blocks an inline onsubmit.
{% endcomment %}
{% endif %}
{% endfor %}
{% else %}
Nobody here yet
Invite the people who answer messages with you.
{% endif %}
Pending invitations
{% if invitations %}
{% for invite in invitations %}
{% include "partials/_nav_icon.html" with name="user" icon_size=19 %}