►
From YouTube: GitLab 13.5 Kickoff - Manage
Description
The Product team for GitLab's Manage stage (including the Access, Analytics, Compliance, and Import groups) assemble to showcase what's ahead for us in 13.5:
- Access: 0:16
- Analytics: 10:39
- Compliance: 18:57
- Import: 24:20
Agenda and issue links are publicly available at https://docs.google.com/document/u/1/d/e/2PACX-1vRnN91k9Rx1AyF8cIQga3KGFpjkI-sheTB16Jg-4e8fO3snZas2Th4hJC5C5wKIrNWbzr8aYDjI-T7-/pub
B
Thanks
matt,
so
let
me
talk
about
some
of
the
things
that
we're
working
on
the
access
team,
so
I'll
share.
My.
B
Screen
yeah,
so
one
of
the
it's
been
a
kind
of
like
a
longer
running
initiative
that
we've
been
doing
is
really
revamping
the
members
list
for
better
usability.
So
I
linked
to
the
issue
where
you
can
see
basically
the
entire
list
of
issues
identified.
B
This
has
been
a
joint
initiative
with
the
growth
team
and
there's
part
of
this
is
that
there
are
several
user
lists
and
they're
not
consistent,
and
just
overall
they
could
be
improved
and
then
also
we
took
this
opportunity
to
change
that
component
to
be
a
pajamas
component
to
play
into
our
larger
initiative.
As.
B
B
This
is
our
existing
list
in
case
you're,
not
familiar
with
it,
your
pretty
straightforward
users
list,
but
there's
actually
a
lot
of
hidden
data
elements
that
are
conditional
sometimes
appear
sometimes
don't
appear,
and
for
a
lot
of
them,
it's
not
very
clear,
even
what
they
are.
So
you
can
see.
This
is
the
new
functionality
so
side
by
side.
B
One
of
the
biggest
changes
is
that
we
have
a
lot
more
columns
right.
So
a
lot
of
the
elements
that
were
sort
of
here
in
this
area
are
now
distinct
columns.
They
all
have
tool
tips.
B
We
worked
on
the
language
for
them
to
try
to
make
it
more
clear.
Of
course,
that's
iterative
and
there's
some
that
we
will
probably
continue
to
work
on
so
just
overall,
more
clear
and
then
doing
this
basically
sets
us
up
to
be
able
to
do
better
filtering
right,
since
we
now
have
more
columns
for
more
data
elements
and
it's
just
overall,
more
usable.
So
the
first
iteration
of
this
is
doing
this
at
the
group
level.
B
So
the
group
members
list
is
the
first
one
to
be
changed
and
then
we'll
move
on
to
project
list
and
also
the
main
users
list
at
the
instance
level.
So
we
expect
that
the
first
iteration
of
this
will
launch
at
13.5,
but,
like
I
said,
there's
it's
going
to
be
in
multiple
phases.
The
first
one
is
the
group
level
list.
B
Another
thing
that
we're
launching
is
project
access
tokens,
so
this
was
launched
ga
for
self-managed
in
13.3,
but
there
were
some
gitlab.com
specific
issues
that
we
needed
to
complete,
specifically
just
around
making
sure
that
this
feature
was
secure
right
and
there's
a
couple
of
things
in
the
back
end
where
we
create
users
and
just
some
considerations
from
gitlab.com
and
to
remind
you
what
that
looks
like
it's
like
this.
B
B
So,
basically,
today
in
self-hosted
instances
there's
an
option
to
enable
what
we
call
open
registration
and
what
that
does
is
that
on
the
sign
in
page,
you
see
a
link
that
says
register,
so
people
can
turn
that
on
or
off,
but
when
it's
on.
Basically,
when
you
register
you're
now
in
the
instance
you're
not
added
to
any
groups,
but
any
groups
that
are
public
in
that
instance,
you
can
see
them
and
interact
with
them.
B
So
what
this
change
will
do
and
there's
no
visuals,
because
for
the
first
duration,
there's
no
ui,
but
basically
what
it
does
is
that
instead
it's
a
configuration
setting
so
that,
instead
of
automatically
being
part
of
the
instance,
you
go
into
a
state
where
you're
waiting
for
approval
right.
So
an
admin
will
get
a
notification
email
that
says.
There's
this
person
waiting
to
be
approved
and
they
can
basically
say
yes
or
no
so,
and
that
user
can't
access
anything
and
they're,
not
billable,
while
they're
in
this
interim
state.
B
A
B
Yeah
sure
so,
basically,
especially
for
large
enterprises,
creating
a
user
in
gitlab
is
actually
a
pretty
big
feat
right,
because
if
you
think
about,
if
your
sso
connected
right,
you're
not
only
having
to
create
a
user
in
gitlab,
but
you
basically
have
to
take
it
as
far
back
to
the
source
of
truth
for
users
right
so.
A
B
Lot
of
times
it
involves
creating
a
user
in
your
active
directory
right,
which
means
they
get
an
inbox
right.
They
basically
are
this
shell
entity,
basically
that
you
have
to
create
all
the
way
back,
and
not
only
is
it
frustrating
right
because
at
that
point,
you're
interacting
with
your
probably
company
id,
and
that
can
take
a
long
time
but
a
lot
of
times.
B
That's,
basically
someone
needs
to
keep
it
right
and
if
it's
associated
to
say,
matt
right,
we
choose
his
account
to
do
automation
with,
if
not
least,
my
team
right.
It's
now
forever
tied
to
him.
So
it's
basically
coming
from
a
few
angles
that
we're
trying
to
solve
here.
One
is
cost
right
of
not
having
to
procure
dummy
accounts
right.
That's
one
thing,
and
the
other
is
basically
giving
people
a
way
to
create
access
to
a
project
without
tying
it
to
an
individual.
A
Yeah,
that's
awesome.
Thank
you
for
that.
That
added
detail.
That's
that's
great!
Nick
harris
any
questions.
C
Yeah
actually,
first
of
all,
I
would
say
kudos
for
the
group
for
actually
looking
at
the
user
experience
and
and
those
tables
with
users
look
great,
and
I
just
look
forward
to
other
issues.
Like
other
lists
projects
and
other
lists,
you
know
getting
the
same
kind
of
treatment
and
getting
the
consistency
and
the
usefulness.
C
So
that's
that's
just
awesome.
Just
really
excited
about
that
and
my
question
is
about
the
project
access
token.
I
wonder,
is
there
any
difference
between
the
access
token.
A
C
You
get
a
project
level
versus
the
access
token
that
you
can
get,
for
instance,
in
terms
of
how
it's
used
or
what
it
can
see
other
than
it's
locked
down
just
to
the
project.
I'm
asking
because
we're
looking
at
using
the
personal
access
token
for
access
for
migrating,
a
part
of
your
gitlab
instance,
and
I
wonder
if
we
should
be
considering
two
different
types
of
tokens
or
is
this
just
kind
of
the
same
as
as
a
token
that
we
previously
had.
B
Yeah,
so
today
you
can
only
generate
tokens
basically
in
the
scope
of
a
user
right,
so
this
kind
of
removes
that
user
tie
right.
This
is
a
token
for
the
project,
but
we
are
looking
at
iterations
of
basically
bringing
bringing
that
up
to
the
group
level
that
that's
the
next
iteration
of
this
and
then
past
that
we
do
have
requests
of
basically
having
a
way
to
generate
an
instance-wide
token.
C
B
Api
calls
and
you
could
derive
what
project
you
belong
to,
but
you
can
only
take
make
operations
within
that
project.
You
can't
do
anything
at
the
group
level.
C
B
Yeah,
the
one
caveat
I
would
say
to
look
into
is
there's
no
way
to
generate
personal
access
tokens
other
than
through
the
ui.
Today
we
do
have
also
future
variations
of
being
able
to
systematically
produce.
B
A
And
one
final
thought
is:
I'm
excited
about
the
product
access
tokens
as
you
and
I
have
talked
about
melissa
but
for
kind
of
the
audience
sake,
because
it'll
just
make
the
credential
inventory
on
gitlab.com,
I
think
easier
to
implement
more
valuable
or
valuable
at
all
for
gitlab.com
customers
so
really
excited
to
see
all
the
implications
of
that
work.
D
Cool
I'll
get
started
and
share
my
screen
cool,
so
in
13.4,
within
the
analytics
space,
we
made
a
lot
of
great
changes
around
mr
analytics
and
the
instance
statistics
as
well,
and
essentially
what
we're
doing
in
this
in
this
milestone
is
following
up
and
expanding
upon
those
features.
D
I've
spoken
with
a
number
of
of
customers
quite
recently,
and
some
of
our
most
valuable
customers
really
rely
on
the
category
of
of
devops
reports
to
get
a
better
understanding
of
how
they're
adopting
git
lab.
What
sort
of
return
on
investment
of
gitlab
is
and
hasn't
seen
much
love
recently,
so
we're
basically
investing
a
lot
of
our
effort.
I'd
say
about
75
of
our
effort.
D
D
So
we'll
start
up
with
instant
statistics
and
I'll
actually
just
show
the
epic,
because
it's
all
related,
but
essentially
the
key
pain
point
here-
is
a
lot
of
our
users
just
generally
want
to
understand
how
they're
trending
and
how
they
are
using
different
areas
of
gitlab's,
most
popular
features,
so
getting
just
an
ad
at
a
glance
view
and
sort
of
understanding
whether
we're
trending
up
and
to
the
right
is
is
is
a
pretty
useful
thing,
so
we
put
together
this
instance.
Statistics
dashboard
and
this
dashboard
is
relatively
simple.
D
We
have
some
of
these
statistics
already
within
the
admin
view,
but
they
weren't
graphed
over
time,
so
we're
starting
to
visualize
this
this
stuff
a
little
bit
more
and
make
it
a
little
bit
better
to
understand
how
we're
trending.
So
the
proposal
is
actually
adding
four
charts
on
top
of
each
other.
We
have
these
metrics
already
and
what
we'll
be
doing
is
adding
these
charts
one
showing
the
number
of
users
in
the
instance
two
showing
the
number
of
projects
and
groups
superimposed
upon
one.
D
Another
three
is
showing
issues
and
merge
requests
superimposed
upon
one
another
and
then
third,
one
is
pipelines
and
pipelines.
We're
actually
gonna
have
two
other
categories
as
well.
One
is
I've
forgotten
the
other
options
of
pipelines,
but
there's
other
stuff
there
and
and
it'll
be
included.
So
that's
that's
sort
of
where
we're
investing
the
effort.
D
A
D
Start
out
with,
we
have
just
released
this
this
chart
and
this
table
and
we've
just
had
the
the
filter
bar
implemented,
where
you
can
filter
things
like
branches
authors,
assignees,
all
this
sort
of
stuff.
So
this
this
table
is
starting
to
become
super
useful
for
developers.
Development
team
leads
getting
a
good
understanding
of
what's
been
closed
within
a
certain
period
of
time,
and
what
we'll
be
focusing
on
this
milestone
is
adding
this
date
picker
here.
D
So
you
have
a
more
specific
slice
of
time
and
also
allowing
us
to
paginate
the
table
as
well
just
making
it
a
little
bit
easier
to
manipulate
the
data,
because,
right
now
it's
just
a
big
old
list
of
100
or
so,
mrs
so
just
improving.
B
D
Usability
in
that
way,
so
those
are
the
key
things
that
we're
focusing
on
within
managed,
analytics
and
I'll
pause
there
and
open.
A
Cool
yeah,
I'm
I'd
love
to
to
hear
a
little
bit
about
some
of
the
inspiration
behind
focusing
on
these
a
little
bit
more
because
I
think
one
of
these
views
is
what
my
group
was
trying
to
use
to
look
at
how
things
were
moving
out
of.
I
think
the
refinement
phase,
because
we
use
like
the
next
up
label
and
stuff,
but
I
think
that
was
I
can't
remember
if
I
was
issue
analytics
or
if
that
was
one
of
these
views
that
you
showed.
A
But
could
you
maybe
talk
about
some
of
the
the
use
cases
there.
D
So
the
use
cases
around
mr
analytics
there
are
a
number
of
them.
The
the
key
metric
that
we're
focusing
on
right
now
is
is
throughput.
So
that's
closed,
mrs.
So
there
are
a
number
of
things
we're
thinking.
This
could
be
used
for
understanding
just
general
productivity,
which
is
the
obvious
one
seeing
what's
coming
through
and
having
filters.
D
So
you
can
sort
of
understand,
specifically
your
team
or
what
what
a
section
or
your
team
is
working
on
understanding
a
little
bit
more
about
the
trend
of
what
is
so
we're
going
to
be
adding
in
things
like
mean
time
to
merge,
so
understanding
the
if
there
are
any
interesting
correlations
between
mean
time
to
merge
and
some
of
the
some
of
the
some
of
the
metrics
within
the
table
and
generally
just
having
a
greater
understanding
of
what's
been
achieved
within
a
certain
time
frame.
D
So
thinking
about
using
this
in
the
context
of
like
retrospectives
or
also
just
sprint
planning
and
so
on,
as
well.
D
A
B
D
Provide
some
feedback
so
yeah
you.
D
C
Hey
nick,
I
want
to
sign
up
to
be
your
lab
rat,
so,
whatever,
whatever
charts
views,
anything
you
feel
like
might
be
useful
to
me.
Please
let
me
know
I
would
like
to
start
dog
footing
it,
and
I
will
give
you
as
much
feedback
as
you
can
take
hope.
The
issue
can
hold
a
lot
of
feedback.
I've
been
I've
been
doing
that
with
with
some
of
the
other.
You
know
elements
of
things
that
I
use
you
know
within
gitlab
and
I
would
definitely
love
to
doc
food
analytics
as
much
as
I
can.
C
Up
until
now,
I
wasn't
able
to
find
a
lot
of
areas
that
were
providing
value,
so
I'm
willing
to
just
look
at
what
you're
working
on
right
now
and
provide
feedback
to
just
get
get
it
to
the
place
where
we
all
get
a
lot
of
value
out
of
analytics.
So
please,
thank
me
all
the
time.
D
B
Yeah
I
just
wanted
to
chime
in
and
say
I
love
the
idea
of
building
reports
to
allow
champions
to
demonstrate
value.
I
think
that's
really
great
right,
because
it's
helpful
for
them
to
see
trends
like
that,
but
it's
also
nice
for
us
right,
because
if
there's
ever
a
question
about
adoption
or
what
value
are
we
getting
out
of
this,
it's
just
super
easily
accessible.
D
Yeah,
I
totally
agree.
I
think
roi
is
like
a
thing
that
I've
heard
customers
talk
about
and
again
and
again,
and
we're
going
to
start
out
by
just
having
our
like
get
lab
adoption
as
a
rough
proxy
for
roi
and
then
use
that
as
a
framework
and
start
building
on
top
of
it.
But
yeah.
Some
of
these.
Some
of
these
charts
that
were
provided
are
hopefully
getting
getting.
Users
to
understand
that
adopting
gitlab
is,
is
useful
in
providing
value
around
cost
savings
and
all
that
sort
of
stuff.
A
A
So
what
we're
focused
on
in
this
release
is
going
to
be
another
iteration
on
the
credential
inventory.
So
a
few
milestones
ago,
we
took
the
opportunity
to
focus
on
the
overall
credential
management
experience
at
gitlab,
trying
to
balance
between
the
generally
disruptive
nature
of
credential
management
and
the
hard
requirements
that
our
customers
have,
and
I
guess
also
like
our
general
stance
of
wanting
to
provide
the
best
developer
experience.
A
So
one
of
those
iterations
is
adding
a
delete
button
to
the
admin
credential
inventory
and
the
reason
we
added
this
and
a
revoke
button
for
personal
access
tokens
was
to
give
flexibility
to
admins,
so
they
can
optionally
enforce
programmatically
the
revocation
of
a
personal
access
token
right
now,
but
one
of
the
pieces
of
feedback
we
received
was
from
some
customers
is
hey.
I
don't
want
to
be
that
disruptive.
A
I
want
to
have
some
say
in
when
that
gets
revoked,
because
maybe
I
want
to
work
with
the
developer
first,
maybe
I
want
to
be
a
bit
more
lenient.
Maybe
I
want
to
give
a
little
bit
of
lag
time,
and
so
adding
these
buttons
is
a
very
simple
intuitive
way
to
empower
an
admin
to
do
that
where
they
will
see
that
a
credential
has
expired.
A
Maybe
they
know
it's
been
compromised
or
they
suspect
it's
been
compromised
and
they
can
go
in
and
just
manually
address
that.
So
that's
what
we'll
be
iterating
on
in
13.5.
In
that
context,
we're
also
working
on
a
foundational
component
to
bringing
this
functionality
to
gitlab.com.
A
There
was
also
like
group
scoped
tokens
that
were
coming
so
when
we
start
aggregating
those
credentials
into
this
inventory,
we'll
then
be
able
to
support
the
revocation
of
those
tokens
in
much
the
same
way
that
self-managed
admins
can
do
today,
we'll
also
be
iterating
on
the
user
list.
So,
along
the
theme
of
access,
where
you're,
trying
to
add
more
value
and
better
clarity
to
these
listings,
this
is
part
of
an
epic
to
eventually
export
a
list
of
all
users
and
the
access
they
have
access
to
within
a
namespace.
A
So
this
iteration
just
simply
tallies
the
total
number
of
groups
and
projects
in
the
admin
views
user
list.
The
value
here
is
that
if
I
know
that
harris
and
melissa
should
only
be
part
of
one
and
three
groups
respectively-
and
I
see
that
you
know
harris
is
part
of
10-
I
can
make
a
very
quick
decision
about.
I
need
to
go
look
into
that.
We'll
then
be
following
that
with
the
ability
to
export
this
data
with
a
much
more
granular
breakdown
of
those
10
groups,
r
groups,
a
b
c
d,
etc.
A
This
is
one
of
the
many
exports
that
our
customers
want
to
be
able
to
compile
evidence
or
evidence
artifacts
themselves
outside
of
gitlab,
since
we
don't
currently
provide
custom,
tailored
or
or
comprehensive
audit
reports.
So
these
are
some
of
those
quicker
wins
we
can
provide
by
allowing
them
to
export
the
data
that
already
exists
within
their
namespace,
so
that
they
can
then
manipulate
or
parse
through
that
in
the
way
that
they
need
to,
and
then
the
the
final
noteworthy
one
is
we're
making
some
ux
and
ui
improvements
to
the
audited
events
table.
A
We've
spent
the
last
several
milestones
working
on
some
refactoring
work
for
audit
events,
the
underlying
model
and
database
table
and
now
we're
incorporating
these
changes
on
the
front
end
to
provide
a
better
experience
and
an
optimized
experience
for
users,
so
that
we're
trying
to
make
it
less
daunting
and
less
frustrating
to
have
to
deal
with
a
slow,
arduous
viewing
or
use
ex
user
experience
on
the
audit
events
table
and
then,
finally,
just
not
in
an
issue
but
or
not
a
single
issue.
A
But
we
have
several
issues
that
we're
working
on:
to
make
improvements
to
things
for
project
deletion
and
then
some
technical
debt
on
the
front
end.
That
should
also
have
the
added
benefit
of
improving
the
overall
ux
for
some
of
the
areas
that
we
manage
or
build.
But
I
think
that's
the
key
highlights
for
the
compliance
group.
Any
questions
or
comments.
B
Just
excited
for
the
inventory
direction
and
hopefully
bringing
that
to
goodluck.com
soon
by
making
a
group
level.
C
Thanks,
so
I'm
going
to
be
talking
about
one
big
nbc
that
we're
going
to
deliver
in
13.5,
and
that
will
be
the
focus
of
the
team
and
we'll
be
swarming
around
this
in
order
to
get
this
mvc
in
place.
So
we
could
then
follow
up
with
many
iterations
to
get
it
to
where
we
need
it
to
be,
so
that
will
be
the
sole
focus,
and
that
is
the
gitlab
group
migration
nbc.
C
Okay,
so
I
want
to
talk
about
the
current
experience,
a
little
bit
sort
of
to
to
point
out
the
pain
points,
and
why
we're
really
doing
this
so
in
today's
world,
when
you
want
to
migrate
a
group
from
one
instance
of
gitlab
to
another
instance,
whether
it's
migrating
from
a
self-hosted
instance
into
gitlab.com
or
maybe
going
from
gitlab.com
into
a
self-hosted
experience
self-managed,
what
needs
to
happen
is
coordination
of
many
different
exports
and
imports
so
for
each
one
of
the
groups
in
order
to
to
get
the
group
imported
in
the
destination,
what
you
have
to
do
is
provide
a
file
which
is
an
export
from
the
originating
instance
that
file
you
can
get
by
going
to
the
group
settings
general,
not
the
most
intuitive
place
to
find
these
things,
and
when
you
want
to
guess
where
it
is
in
here
it
is
under
advanced.
C
We
expand
that
scroll
down
hit
export
group,
which
will
then
kick
off
a
file
creation.
Once
that
file
is
created,
you
will
have
to
save
it
somewhere
locally
and
then
attempt
an
upload
here.
What
happens
in
these
so
that
file
will
contain
just
the
group
level
info.
It
will
not
contain
any
of
the
subgroups,
it
will
not
contain
any
of
the
projects
and
any
of
the
data
hangs
off
of
that.
So
you'll
get
the
epics,
but
not
the
issues.
C
For
example,
in
order
for
you
to
migrate
the
entire
group
with
all
the
projects
that
belong
to
it
from
one
instance
to
another,
you
will
need
to
export
each
project
individually
and
the
group
overall
and
then
kind
of
reassemble
that
on
the
back
end
by
importing
the
group
and
then
importing
new
projects,
this
is
very
complicated.
As
a
you
know,
it's
definitely
not
something
that
many
people
can
self-serve,
especially
if
they
have
large
groups
or
large
projects
or
a
large
number
of
groups
and
projects.
C
C
These
files
can
get
quite
large,
so
we're
sometimes
talking
about
gigabytes
being
uploaded,
and
you
know,
there's
network
issues
and
all
kinds
of
problems
that
come
with
that
that
that
kind
of
break
the
ability
for
people
to
do
this,
you
know
so
in
addition,
so
in
order
to
overcome
that
and
to
make
this
so
that
anyone
can
move
their
groups
and
projects
from
any
instance
of
gitlab
to
under
instance,
of
gitlab,
we
are
going
down
the
path
of
creating
a
gitlab
entire
group
migration,
which
is
going
to
be
similar
to
what
we
already
have
for
bitbucket
and
github.
C
In
those
cases
we
just
point
at
a
project
in
github
and
it's
kind
of
an
api,
all
it's
a
server
to
server
communication.
You
have
to
download
anything
intermediate,
but
any
intermediate
files.
You
have
to
upload
anything.
It
is
one
instance
talking
to
another
and
the
data
streams
across
which
is
faster
and
much
more
reliable.
C
So
the
first
step
for
us
is
to
add
a
new
is
to
add
a
new
way
of
doing
group
imports.
So,
in
addition
to
the
file
based
import,
we're
now
adding
the
ability
to
to
provide
a
url
for
the
source
instance
of
lab
and
a
personal
access
token,
which
ties
into
what
I
was
asking
the
list
about
earlier
and
authenticate
with
that
other
gitlab
instance.
C
In
the
end,
the
goal
is
for
that
to
migrate
everything
that
hangs
off
of
that
group,
including
all
the
projects
and
all
the
subgroups
and
projects
to
hang
off
of
that
for
the
mvc.
C
We
are
selecting
only
to
import
one
group
at
a
time
and
the
only
the
only
data,
in
addition
to
kind
of
the
group
metadata
that
will
be
imported,
that
hangs
off
of
that
party
epics,
so
you'll
be
able
to
initiate
a
group
migration
for
the
nbc,
provide
the
credentials,
see
the
list
select
one
group
and
that
group
will
then
be
recreated
on
the
instance,
and
we
will
then
migrate
any
epics
that
hang
off
of
that
group.
So
that
will
be
the
nbc.
C
It
is
a
pretty
lofty
goal
and
there
are,
as
you
can
tell
there's,
there
are
a
lot
of
issues
that
hang
off
of
that
they're
all
scheduled
for
13.5.
So
the
team
is
committed
to
delivering
this
nbc
at
the
end
of
13.5,
where
we'll
be
able
to
do
the
one-click
migration
of
an
entire
group
with
its
epics
and
from
then
on
we'll
just
iterate
and
start
adding
more
detail
until
we
have
a
product
that
people
would
love
to
use.
C
D
I
I
I
reviewed
the
experience
that
that
amanda
created
and
it's
it's
really
nice,
it's
it's
it's
great
bit
of
ux.
I'm
wondering
that
right
now
it
doesn't
seem
like
there's
an
apparent
way
or
easy
way
for
for
us
to
dog
food.
This,
but
have
you
got
any
recommendations
for
how
we
could
dog
food
this
and
provide
feedback.
C
I
have
not
come
up
with
a
good
like
scenario
where
we
would
internally
need
to
use
this.
However,
I
am
working
with
the
professional
services
group
that
has
built
a
tool
called
congregate
and
the
reason
for
why
that
tool
was
built
is
because
we
didn't
have
this
in
place.
So
if
we
had
this
in
place,
we
probably
wouldn't
have
built
out
a
tool
that
all
it
does.
C
Is
it
just
kicks
off
all
these
exports
for
groups
and
all
the
sub
projects,
stores
them
and
stores
them
somewhere
and
then
kind
of
tries
to
re-import
those
in
the
right
spot
and
then
put
put
the
things
back
together.
So
that
was
the
original
goal
for
the
congregate
and
what
we'll
be
doing
is
we
will
hopefully
be
replacing
some
of
the
pieces
and
some
of
the
logic
from
congregate,
with
this
new
logic
and
congrats
will
be
a
lot
more
lean
and
and
not
not
have
to
know
as
much
about
business.
C
So
I
expect
the
professional
services
and
the
congregate
team
to
be
kind
of
the
the
doc
the
team,
the
dog
foods
this
for
us
internally.
C
B
C
C
A
Yeah,
I
think
that's
excellent,
well
done
harris
and
your
whole
group.
I
think
that
pretty
much
wraps
us
up
unless
there
are
any
final
questions
or
comments
about
anything.
A
Cool
and,
if
not
great,
to
see
everyone
thanks
for
another
great
kickoff
video,
I'm
excited
for
what's
coming
in
thirteen
five
and
what's
the
the
adage
is
like
the
best
release
ever
is
coming
up.
So
I'm
excited
for
everything
and
you
all
have
a
great
rest
of
your
day.