►
From YouTube: GitLab 13.3 Kickoff - Manage:Access
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
The
first
one
is
that,
as
you
may
have
seen
in
other
kickoff
videos,
I
get
lots
working
on
expanding
on
the
integration
with
the
Atlassian
suite
and
the
access
team
is
building
a
features.
That's
foundational
to
make
this
all
happen.
So
what
this
will
do
is
that
it
will
allow
us
to
link
a
user
to
link
their
get
level
account
to
their
Atlassian
cloud
account.
It
will
likely
look
a
bit
like
these
other
integrations
that
we
have
where
users
are
able
to
basically
connect
different
accounts.
A
So
what
this
functionality
will
do
is
that
it
sets
the
stage
and
it's
a
foundational
piece
for
presenting
product
data
inside
of
gitlab.
So
you
can
imagine,
users
will
be
able
to
see
a
JIRA
issue
list
and
compensated
right
in
line
with
gitlab.
So
this
piece
has
the
stage
to
make
that
all
happen.
So
it's
very
exciting
and
the
next
one
is
around
our
SSO
functionality
on
Caleb
comm.
A
So
in
talking
to
customers,
we
found
that
they
needed
more
flexibility
in
the
way
that
our
SSO
product
for
today,
particularly
around
one
piece,
which
is
that
all
once
they
said
SSO
up
in
a
group,
all
users
that
SSO
in
our
added
us
guests
at
the
top
level,
which
gives
them
guest
access
to
everything.
In
that
hierarchy.
A
Customers
indicated
that
there
are
portions
of
what
the
data
they
keep
and
good
love
that
they
want
to
be
able
to
keep
secret.
This
can
be
friendly,
a
purposes
for
audience
reasons,
really
there's
a
lot
of
different
reasons
why
they
want
to
do
that,
and
so
we
are
building
two
features
that
will
help
to
achieve
that
in
this
milestone.
One
of
them
is,
as
you
read
here,
is
to
be
able
to
add
at
the
top
level
group
and
give
no
access
below.
A
So
basically,
what
that
will
allow
our
customers
to
do
is
to
add
users
in
any
part
of
the
hierarchy
below
at
any
level.
So,
basically,
you
give
very
granular
access
to
just
what
they
need,
and
the
other
part
of
this
is
to
be
able
to
set
a
default
role
when
you
SSO
in
so
you
may
be.
We
also
found
that
there
are
some
companies
that
are,
you
know,
would
love
to
open-source
their
whole
hierarchy
and
really
guess
is
not
permissive
enough.