►
From YouTube: GitLab 12.7 Kickoff - Manage:Access and Manage:Analytics
Description
See more of what's in store in 12.7 in our Kickoff Playlist: https://www.youtube.com/watch?v=NLGs21eG5Lk&list=PL05JrBw4t0KrC_-b7EXgwskea86uF3yK4
A
Hey
everyone,
I'm
Jeremy,
I'm,
her
product
manager
here
get
lab
helping
represent
the
managed
state
to
the
balance
life
cycle
I'm
here
to
talk
a
little
bit
about.
What's
in
the
store
for
12.7,
releasing
January,
22nd
and
I'll,
be
talking
a
little
bit
about
the
analytics
and
access
groups
and
what
we
plan
on
working
on
I'm
gonna
start
with
access
and
I'm
gonna
go
ahead
and
share
my
screen
and
talk
through
a
few
issues.
A
So
the
first
issue
that
we're
excited
to
kind
of
iterate
on
is
sam'l
SSO
and
gate
lab
comm.
So
one
challenge
that
we're
trying
to
make
a
little
bit
easier
is
to
make
troubleshooting
and
configuration
simpler
for
administrators.
One
challenge
that
we
know
about
is
managing
user
identities
can
sometimes
a
challenge.
We
are
including
the
ability
to
list
and
remove
user
identities
when
helping
try
to
understand
challenges
when
configuring
a
sam'l
SSO.
A
So
in
this
release,
we're
going
to
list
out
the
the
connected
identity
is
that
users
configure
and
map
to
the
group
when
they
are
SS,
owing
into
the
particular
to
the
top-level
group
list
them
here,
along
with
their
connected
identity,
that
you
could
actually
remove
to
to
kind
of
troubleshoot
problems.
This
is
really
useful
when
a
user
it
has
is
having
trouble
signing
in
you
can
simply
can
remove
the
identity
they
can
SSO
back
into
the
account
and
restore
the
connection.
A
So
so
we're
also
integrating
on
the
concept
of
group
managed
accounts,
which
is
a
useful
tool
when
using
in
the
enforcing
SSO
on
a
top-level
group
of
gitlab
comm
group
managed
accounts,
allows
you
to
require
a
user
to
actually
create
a
dedicated
user
account
for
use
with
that
particular
group,
and
we
want
to
extend
the
concept
of
group
managed
accounts
a
little
bit
further
to
allow
organizations
to
enforce
behavior
on
these
users
that
are
actually
that
are
created.
Specific
accounts
for
your
enterprise.
A
So
one
thing
that
we'll
will
do
is
allow
a
group
owner
to
actually
toggle
whether
or
group
managed
accounts
or
able
to
create
Forex
outside
of
the
group.
One
challenge
that
enterprises
have
is
a
managed
account
that
is
using
a
that
is
using
get
lab.
Comm
can
actually
fork
an
enterprise
or
organizational
project
into
their
personal
namespace,
which
that
organization
no
longer
has
control
over
or
audit
capabilities.
A
So
in
this
iteration
in
this
change,
what
we
want
to
do
is
actually
disable
that
ability
and
and
enforce
the
that
group
managed
accounts
will
only
be
able
to
fork
somewhere
within
that
account
within
that
group.
Another
thing
that
we
want
to
do
with
the
go
with
group
managed
accounts
is
also
prevent
projects
from
being
shared
outside
of
those
accounts
in
get
lab,
you're
able
to
actually
create
project
shares
and
those
project
shares
can
be
shared
with
groups
anywhere
on
the
instance
since
get
lab.
Comm
is
a
large
get
level
to
the
instance.
A
One
challenge
is
being
as
organizations
losing
control
of
their
projects
by
accidentally
sharing
projects
kind
of
outside
of
that
namespace.
So
once
again,
we
want
to
continue
to
iterate
on
the
concept
of
security
and
for
group
managed
accounts.
We
actually
want
to
prevent
any
organization
from
sharing
a
project
kind
of
outside
that
group
I'm,
going
to
keep
everything,
name,
spaced
and
controlled
within
the
confines
of
that
top-level
group.
A
So
you
know
we
continue
to
kind
of
invest
in
in
sam'l
basis
to
so
and
I
think
that
we're
we're
excited
to
continue
to
iterate
on
this
concept
of
group,
managed
accounts
and
kind
of
increase,
the
amount
of
security
and
control
that
organizations
using
it
kind
of
path.
So
that's
a
that's
it
for
access.
I'm,
gonna,
move
over
to
analytics
and
I'm
excited
about
two
for
two
really
interesting
changes
and
the
first
one
is
we're
excited
it
going
to
create
an
analytics
area
in
the
project
sidebar.
A
You
know
at
the
moment
we
have
kind
of
analytics
feature
related
features
that
are
kind
of
scattered.
Here
we
have
one
in
cycle
analytics.
There's
one
could
hear
under
CI
CD
under
charts.
There's
one
here
under
under
charts
here
in
the
repository
and
what
we
want
to
do
is
we
want
to
create
a
dedicated
area.
A
So
the
proposed
approach
is
to
add
a
project
level,
new
feature
which
defines
review
time
as
the
time
it
takes
from
the
first
from
the
first
line,
comment
in
an
emergent
to
the
time
that
it
is
merged
and
better
understanding
how
long
that
is
taking.
So.
The
first
iteration
is
a
simple
table
and
where
we
are
sorting
by
default
by
review
time.
So,
at
the
project
level
immediately,
it
becomes
very
easy
to
understand
which
merge,
requests
are
kind
of
lagging
behind
and
may
require
additional
support
in
order
to
get
to
the
finish
line.
A
This
is
going
to
be
in
get
labs,
starting
and
I.
Think
is
going
to
be
the
start
of
a
more
focus
that
we
place
on
specific
analytics
features
that
are
that
are
in
cycle
analytics.
I,
think
you
know
we
are
kind
of
diving,
deeper
into
different
stages
in
cycle
analytics,
starting
with
code
review
and
then
iterating
to
other
parts
of
the
value
stream,
so
really
excited
to
kind
of
get
this
MVC
out,
get
it
into
your
hands
in
January
and
see
what
you
think,
but
overall
I
think
there's
a
lot
of
exciting
stuff.