►
From YouTube: UX Showcase What is an organization
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
All
right,
Mike,
Nichols
staff,
product
designer
working
on
manage
organize
and
we're
going
to
talk
about
what
an
organization
is
today
so
real
quickly.
The
workspace
group,
formal
formally
workspace
group,
is
now
called
the
organization
group
announced
it
on
slack,
but
just
another
Public
Service
Announcement
here
also
a
couple
of
things:
user
profile
and
topics
turns
out.
We
are
responsible
for
those.
We
don't
spend
much
time
working
on
those,
but
technically
those
do
fall
to
our
group.
So
a
little
Public
Service
Announcement
there
all
right.
A
A
No,
so
we
like
I,
said
we've
recently
renamed
the
the
group
organization,
but
we
also
are
renaming
the
feature
workspace
to
an
organization
so
for
a
slightly
better
answer
than
that.
Let's
look
at
all
of
the
containers
and
see
how
they
fit
together
and
you're.
Gonna
hear
me
see
the
word
containers
a
lot.
A
A
So,
first,
let's
take
a
look
at
a
project.
What
is
a
project?
It's
a
place
to
do
work,
it's
a
place
to
track
work
and
it's
a
place
to
manage
your
work,
things
like
settings
and
permissions.
It's
really
a
convenient
oops
just
got
changed.
That's
a
yeah!
Sorry
that
slide
got
changed,
but
it's
really
just
a
way
of
applying
settings
and
tracking
things
across
the
project.
Its
scope
is
the
project
itself.
That's
where
it's
concerned
is
it's
related
to
the
project.
A
A
A
It
also
has
a
few
extra
things
in
it
like
a
place
to
manage
members
and
it's
a
place
to
manage
your
subscription.
So
it
is
the
place
to
track
and
manage
all
projects.
It
is
aligns
with
the
needs
of
a
company
more
so
than
a
group
or
project.
It's
more
focused
on
the
company
needs,
and
this
is
true
on
SAS,
not
necessarily
on
self-managed.
A
So
what
is
the
admin?
So
it's
an
additional
way
to
track
work
across
some
of
the
projects.
It
does
have
a
few
additional
settings
place
to
manage
users
subscription
it
also
what
it.
What
what
top
level
groups
don't
have?
Is
it's
a
place
to
manage
your
instance
itself,
so
some
of
the
settings
that
apply
to
how
your
instance
actually
runs.
A
So
it's
a
place
to
track,
but
mostly
manage
all
of
the
projects
and
it
is
aligned
with
the
needs
of
the
company
on
self-managed,
so
with
all
of
those
in
place.
What
is
an
organization
well
I
think
the
easiest
way
to
explain
that
is
to
go
back
to
a
top
level
group
and
let's
make
a
few
edits
here.
So
what
is
an
organization?
It
is
a
top
level
group,
it
will
be
replacing
top
level
groups
and
then
you'll
notice,
the
plus
signs
here
here
and
here.
A
A
A
So
let's
look
at
this
from
a
feature
perspective.
So
the
first
thing
you'll
notice
is:
it
is
a
lot.
So
what
we're
looking
at
here
is
the
G's
I
mean
it
comes
from
a
group
and
a
means.
It
comes
from
admin
and
a
b
means
that
it's
in
both.
So
you
can
see
there
is
a
decent
amount
of
overlap.
A
Most
of
the
additions
feature
wise,
are
kind
of
in
the
manage
grouping
here
and
more
on
what
these
groupings
are
about
on
the
upcoming
slides.
But
one
thing
that
was
interesting
as
I
was
putting
this
together.
Chris
actually
noticed
this
was
we
often
talk
about
organizations
as
adding
admin
functionality
into
top
level
groups,
but
we
also
see
here
there's
a
lot
of
things
in
groups.
That's
actually
moving
up
to
up
from
the
group
level
so
by
the
combination
of
a
top
level
group
and
an
admin
you're,
actually
getting
a
lot
of
functionality.
A
That
groups
do
that
admins.
Don't
so
that's
a
look
at
it
from
the
feature
perspective.
So
what
does
an
organization
look
like?
Let's
look
at
some
UI,
so
to
do
that.
First,
we
want
to
start
with
the
top
level
group,
since
that's
kind
of
what
it's
based
off
of
and
for
the
sake
of
production,
I've
stopped
using
the
old
menus
and
I've
started
using
the
new
menus
from
the
navigation
work
that
the
foundations
team,
mostly
because
of
the
groupings
that
I
mentioned
earlier.
A
It
just
makes
it
easier
to
work
with
and
we'll
go
from
there.
So
if
you
haven't
seen
this
before,
this
isn't
necessarily
suggested
that
this
is
from
the
organization.
This
comes
from
the
the
foundations
team
in
the
navigation
work
that
they're
doing
here.
A
So
if
we
have
the
group
from
a
based
on
the
new
navigation,
first,
we're
going
to
re-label
and
we're
going
to
add
in
a
few
features
from
the
admin.
So
an
example
here
is:
if
we
have
an
existing
grouping,
let's
say
analytics.
This
is
just,
for
example,
I,
just
kind
of
pulled
one
out
this
grouping
here
analytics
has
a
few
things
in
there.
A
One
of
the
things
that
admin
has
that
groups
do
not
is
devop
reports,
so
some
things
would
just
be
straight
additions
of
features,
in
other
cases,
we're
going
to
need
to
add
in
whole
sales
sections.
So
in
this
case
the
the
manage
section
that
we
talked
about
earlier
also
the
possibility
of
a
system
down
there,
but
in
general,
as
we
move,
these
features
over
almost
all
of
them.
A
Well,
most
of
them
are
going
to
be
straight
one-to-one,
copies,
meaning
like
if
a
screen
looked
like
this
in
the
admin
and
it
moves
over
into
an
organization.
It's
going
to
stay
very
much
the
same,
there's
not
necessarily
A
need
to
to
redo
those.
Eventually,
we
might
want
to
look
at
redoing
some
of
these
pages,
but
it's
not
necessarily
part
of
this
process.
Here.
A
Also
of
note
like
while
topics
is
something
that
the
organization
group
does
most
of
these
screens
are
not
our
responsibility
so
like
let's
say
if
it
was
a
CI
CD
screen
that
moving
process
and
that
redesign
ending
tweaks
that
would
need
to
be
made.
That
would
be
on
the
CI
CD
team,
not
not
necessarily
on
us,
but
there
are
a
few
features.
A
These
are
mostly
the
ones
if
we
go
back
to
the
categorization,
the
both
where
sometimes
there
is
a
feature
at
the
group
level,
and
there
is
a
feature
at
the
admin
level
that
basically
do
the
same
thing.
Members
and
users
is
kind
of
an
example
of
that.
There's
a
membership
screen
at
the
group
level.
There
is
a
user
screen
at
the
admin
level.
A
So
everything
I've
been
mentioning,
has
kind
of
been
talking
about
like
features
by
features.
I
mean
like
things
that
are
actually
in
the
left-hand
navigation,
but
everything
I
just
said
also
applies
to
settings
mostly
what
what
is
in
the
admin
is
setting.
So
the
settings
is
going
to
get
a
quite
a
few
more
settings
compared
to
the
groups
from
the
admin
settings.
This
is
still
a
bit
of
a
work
in
progress
there.
As
you
can
see,
there
is
a
lot
of
items
on
there.
A
So
how
do
you
get
to
an
organization?
So
again,
I
am
leveraging
the
new
navigation
here.
So
apologies-
if
you
haven't
seen
this
before-
and
this
is
all
a
little
confusing,
but
we're
exploring
a
number
of
ways-
one
it'll
probably
be
the
root
item.
In
the
breadcrumbs
we
have
looked
into
an
admin
specific
flow,
that
kind
of
replicates
what
self-manage
gets
now
giving
them
a
way
back
to
the
organization.
A
Keeping
that
consistent
experience
and
we've
also
looked
at
the
groups
in
the
projects
page,
there
might
be
an
opportunity
to
leverage
those
pages
is
kind
of
Anchor
Point
to
show
the
the
groups
mostly,
but
also
projects
kind
of
stem
from
the
organization.
So
we
might
add
them
in
on
that
page
as
well.
A
A
Let
me
expand
on
that
one,
a
little
bit
so
efficiency
is
normally
talked
about
as
engineering
efficiency,
so
right
now
we're
building
things
sometimes
up
to
three
times
at
three
different
levels,
which
obviously
requires
a
lot
more
engineering
work
by
combining
these
together
in
a
single
object
that
applies
to
both
self-manage
and
that
we'll
be
able
to
reduce
engineering
time,
but
that
also
applies
to
like
documentation,
design
work,
just
tracking
things
and
not
just
like
existing
features
and
more
people
getting
more
access
to
it
as
we
improve
those
features
over
time.
A
So
really
is
a
an
efficient
way
to
kind
of
streamline
the
work
and
stop
building
things
multiple
times
to
a
user.
What
it
really
is
is
it's
an
anchor
that
solves
a
lot
of
indirect
user
experience
problems
so
by
the
lack
of
the
existence
of
kind
of
a
true
root
home,
a
few
user
experience.
Problems
have
popped
up,
so
this
will
be
kind
of
the
solution
to
those,
although
not
directly
related
to
them.
It
will
allow
us
to
indirectly
back
solve
those.
So
really,
what
is
an
organization?
A
It's
the
container
that
gitlab
has
been
missing
so
thanks
to
everyone,
who's
been
working
on
this,
especially
Christina.
My
PM
we've
been
fighting
the
fight
on
this
and
doing
a
lot
of
work
on
this,
and
she
has
joined
the
team
and
and
really
helped
us
get
there,
but
also
Nick
I've
been
collaborating
very
heavily
with
him,
and
obviously
all
of
the
screens
that
you
saw
were
based
on
his
work
and
all
of
the
foundations
team
really
is
mostly
the
UI
that
I'm
wearing
work
working
with
there.
B
First
of
all,
thanks
for
this,
this
is
a
huge
body
of
work
and
one
I've
been
very
interested
in
for
a
long
time,
I'm
curious
about
user
Management
on
the
organization
level
and
how
that
will
work,
whether
whether
it'll
be
more
similar
to
a
group
today,
where
you
can
only
manage
direct
members
versus
admin
users,
which
is
a
sort
of
aggregate
of
all
users
anywhere
within
the
within
the
instance,
yeah.
A
So
I'm
glad
you
brought
that
up
or
maybe
not
glad
you
brought
that
up.
A
I
was
making
this
presentation
they
dawned
on
me
that
we
had
been
talking
about
the
possibility
of
memberships,
and
that
might
be
one
of
the
first
things
we
move
over,
but
based
on
our
inheritance.
That
does
set
up
a
bit
of
a
problem.
A
A
So
it's
likely
going
to
be
more
of
the
user
management
that
exists
in
the
current
admin
and
membership
probably
won't
be
a
possibility
at
the
organization
level
or
we'll
just
have
to
make
it
so
it
doesn't
inherit.
But
that
has
this
problem
since
own
right
and
that
then
you'd
be
able
to
see
everything
that
rolls
up
there.
So
it
gets
into
a
bit
of
a
British
problem,
so
it
more
than
likely
is
going
to
have
to
be
just
users
there
and
not.
Actually,
members.
B
Yeah
I
was
going
to
ask
about
inheritance
because
I
think
that's
that's
something.
We
see
a
lot
of
confusion
about
with
SAS
customers
that
they
expect
to
sort
of
have
a
like,
like
admin
users
list,
but
because
of
inheritance
on
top
level
groups.
That's
not
what
they're
seeing
on
the
top
level
groups
members.
B
A
D
Yeah
thanks
so
I
can
see
how
this
makes
it
valuable
to
specifically
like.com
users,
because
some
of
these
admin-like
features
are
kind
of
tracked
in
the
admin
area.
But
I
was
curious.
D
Mike
if
you
have
thought
through
like
how
will
this
be
handled
for
self-manage,
so
I
remember,
there
was
like
a
community
contribution
around
adding
topics
to
the
admin
area.
The
goal
was
to
make
it
so
that
you
could
have
these
Universal
topics
accessible
to
every
project.
So
if
I
was
a
self-managed
user
or
something
self-managed,
administrator
and
I
wanted
to
create
topics
for
all
of
my
projects,
how
would
I
do
that
is
like
a
root
Organization
for
just
self-manage
or
how
does
that
work?.
A
Yeah,
so
that
is
one
of
the
last
sticking
points
that
we
have
is
trying
to
figure
out
how
to
how
to
deal
with
self-management
and
mostly
the
migration
process,
of
it
long-term
think
of
admin
going
away.
Although
that's
not
entirely
true,
because
you
still
need
to
have
like
some
admin,
for
instance,
for
like
Hardware
settings
and
things
like
that.
But
really
it
would
be
a
a
replacement
of
that.
A
So
it
will
be
all
the
features
in
admin
will
now
go
to
organization,
in
fact
that
that
admin
Link
in
the
sidebar
eventually
will
probably
go
to
the
organization
not
to
what
is
known
today
as
the
admin,
and
so
while
that
in
itself
isn't
necessarily
a
benefit
to
self-managed
users.
I
think
they'll
get
their
benefits
from
two
places,
one.
A
They
said
the
efficiency
of
us
developing
things
right
so
as
as
features
get
developed
a
lot
of
times,
they'll
get
developed
at
the
group
level
and
those
improvements
won't
make
their
way
into
the
corresponding
screen
in
the
admin
level.
So
they'll
get
feature
improvements
along
the
way,
but
also
what
I
was
mentioning
about
the
groups
having
a
central
localized
place
to
see.
A
Like
we
got
a
little
out
of
requests
of
like
we
want
to
add
this
kind
of
tracking
when
I
say
tracking
I
mean
things
like
ethics
and
Milestones,
and
things
like
that
things
that
don't
exist
that
exist
at
the
group
level,
but
don't
exist
at
the
admin
level,
even
though
they
technically
do,
because
you
do
have
a
top
level
group
and
in
theory
you
could
see
all
that
that
lack
of
a
centralized,
Anchor
Point
it
kind
of
makes
it
seem
like
there
isn't
a
way
to
track
all
of
that
stuff.
A
D
Okay
gotcha,
so
it
sounds
like
you
still
gotta
think
through
some
of
the
Kinks
of
it,
but
there
will
be
hypothetically,
like
one
organization,
Boxing
Around
everything,
so
there's
still
that
level
of
power.
I
guess
you
could
say,
because
I
feel,
like
the
git
lab
administrators,
still
need
to
control
that
level
of
gitlab.
Even
if
it's
not
Hardware,
it
could
just
be
like
the
sign
in
message
or
if
you're,
a
self-managed
user,
and
you
want
to
have
topics
for
every
single
project.
A
Yeah,
and
also
like
users
that
aren't
in
your
organization,
which
sounds
like
a
weird
well,
how
would
anybody
do
that,
but
especially
on.com?
There
are
non-
they're.
They
belong
to
no
group
at
this
point
user,
so
yeah
there'll
always
be
some
that
are
outside
the
organization,
but
by
and
large
you'll
Set,
like
you,
said,
your
sign-in
screen
and
all
that
stuff.
All
your
preferences
and
all
that
thing
that
will
all
move
into
the
organization
into
a
centralized.
C
I
have
an
extra
question:
I'll
be
really
quick.
It's
just
wondering
how
it
communicates
those
like
cool
changes
to
the
user
like
most
of
them,
I
think
are
self-explainable
but
explorable
by
the
user
and
maybe
like
we
can
assist
them
anyway
in
the
UI,
or
just
mainly
release
posts.
A
It's
the
plan
until
earlier
this
week
was
to
replicate
features
in
the
admin
and
in
the
organization
allowing
them
to
kind
of
not
need
to
make
the
transition
until
the
transition
happens,
and
when
that
transition
would
happen,
we
basically
would
replace
the
links
of
admin
and
go
to
that.
Unfortunately,
that
might
prove
to
be
a
bit
of
an
engineering
challenge.
A
So
what
we're
not
trying
to
do
is
in
a
world
where
we're
trying
to
get
more
efficient
and
write
less
code,
not
write
a
whole
bunch
more
code
for
the
transition
period
that
ultimately
becomes
dead
code.
So
we
don't
know
we're
trying
to
figure
that
one
out
right
now
we
thought
we
had
a
plan
on
that,
but
engineering.
It
might
very
well
be,
as
you
described
kind
of
when
features
get
moved
over
there,
there's
kind
of
a
hot
spot
or
like
a
relocation,
kind
of
message,
type
of
thing
there,
but
TBD.
C
Yeah
cool,
like
just
some
idea
that
I
was
thinking
because
I
did
similar
things
with
the
deprecation
features
that
like,
since
we
are
very
open
with
our
issue
with
new
features,
is
there
a
possibility
that
we
have
a
blog
post
or
something
to
the
user
like
upcoming
months?
Those
will
be
changed
so
they're
prepared
of
something
it's
like
major
changes
like
this.
So
that's
a
possibility,
maybe
to
consider.
E
A
No,
not
necessarily
there
was
a
when
we
when
we
went
through
the
rename.
There
was
a
lot
of
research
that
was
done
there
about
the
naming,
and
there
currently
is
a
somewhat
parallel
effort
going
on
as
the
pods
is
very
dependent
on
organizations
or
could
leverage
it
I
guess.
Maybe
it's
a
better
way
of
saying
that
so
we're
trying
to
get
kind
of
a
sentiment
read
of
the
impacts
of
this
and
that
we
haven't
done
a
tremendous
amount
of
testing.
A
E
Could,
if
there's
time
at
the
end,
like
add
some
questions
or
say
you
know,
I
want
to
switch
gears
entirely
now
and
just
show
you
something
that
another
team
of
ours
is
working
on,
and
can
you
say
something
about
how
this
would
impact
you
as
a
security
engineer
or
something
like
that,
like
I,
don't
know
if
that's
would
be
interesting
to
you
or
helpful,
but
I
wanted
to
put
that
out
there.
It's.
A
A
I
will
say,
though,
most
of
what
we
did
is
based
on
five
or
so
years
of
issues.
So,
while
it's
not
solution
validation,
it
was
the
first
thing
we
did
was
collect
the
list
of
problems
that
have
Arisen
and
we
use
that
as
kind
of
a
driving
force.
I.
E
Know
my
comment
in
the
agenda
first
said:
have
you
done
problem
or
solution?
I'm
like,
of
course,
they've
done
problem
validation?
That's
where
this
whole
project
came
about
is
massive
amounts
of
problem
validation.
Yes,
cool
well,
I'll
reach
out.
You
know
if,
if
and
when
or
when
I
put
that
study
together
that
moderated
study,
maybe
I'll
include
something
about
this,
if
that,
if
it
makes
sense
or
if
that
would
be
helpful,
but
just
kind
of
a
gut
check.