►
From YouTube: RBAC prototype walk through
Description
Daniel Mora goes through our first iteration of a new customizable RBAC interface we are working on. See related epic for more detail: https://gitlab.com/groups/gitlab-org/-/epics/7420
A
A
You
would
go
to
a
new
section,
labeled
roles
and
permissions.
This
we're
still
looking
for
feedback
on
the
title
from
here.
You'll
have
the
current
default
gitlab
permissions
and
then
the
idea
you'd
have
a
container
separate
from
them
to
manage
your
your
organization's
permissions
or
roles,
and
that
way
we
can
at
least
keep
them
separate
and
have
a
way
to
troubleshoot
or
to
reset
permissions
if
needed
here,
we'll
have
the
permissions
library
similar
to
what
we
have
in
documentation
just
with
every
permission
available.
A
Let's
pretend
we
call
the
role
incident
manager
will
give
it
a
base
for
all
of
developer,
based
off
of
what
the
current
gitlab
feature
excuse
me
role
is
so
here
we'll
have
the
list
of
permissions
that
are
allowable
in
that
environment.
That
received
me
in
that
role
and
here's
the
the
new
role
that
we're
making
and
so
we'll
have
this
one,
for
example,
where
a
developer
does
not
have
the
ability
to
delete
epics.
So
let's
say
we'll
allow
that
then
we'll
save
and
now
you've
created
a
new
role,
labeled
incident
manager
here.
A
And
now
we
have
this
new
role,
our
cv
new
member,
with
this
new
role
that
did
not
exist
before,
and
that
is
the
way
that
the
our
back
flow
should
work
at
our
first
iteration.
So
we're
looking
for
feedback
from
this
point
to
see
what
makes
sense
and
what
is
lacking
and
what
might
not
be
currently
included
in
this
demo.