►
From YouTube: PnP Webcast - Site collection app catalog
Description
PnP Webcast around the site collection app catalog, which provides you capabilities to have scoped deployment of SharePoint apps/add-ins or SharePoint Framework solutions.
Site collection app catalog is enabled in site collections by tenant administrator. After this site collection owner can deploy add-ins or SPFx solutions to be available in the specific site collection.
A
Welcome
to
the
SharePoint
patterns
and
practices
webcast
and
this
time
we'll
have
a
look
on
the
site:
collection,
app
catalog
for
shipment
events
and
shipment
frame
resolution.
This
is
a
great
new
capability
which
is
giving
you
the
option
to
target
your
solutions
and
serpent
framework,
add-ins
and
SharePoint
framework
solutions
in
a
more
scope
to
way,
and
also
dedicating
the
let's
say,
management
of
these
solutions
for
site
collection,
administrators.
A
B
A
Thank
you,
one
Langan
and
really.
The
key
point
to
understand
here
is
that
this
site
collections,
scoped
app
catalog,
does
support
both
SharePoint
audience
and
SharePoint
framework
solutions.
So
you
can
absolutely
use
to
absolutely
use
this
capability
for
pause
and
their
classic
well.
I,
wouldn't
say
then
classic
shape
on.
That
is
the
shape
of
talents
and
also
for
SharePoint
framework
solution,
and
how
does
it
actually
work
in
practice?
A
Now
these
capability
enables
and
people
to
target
those
add
in
some
solutions
in
a
site
collection
level,
but
to
be
able
to
do
so.
The
tenant
administrator
first
has
to
enable
that
capability
in
the
specific
site
collection.
So
it's
not
intended
to
be
used
across
all
of
the
site
collections,
because
that
probably
doesn't
make
that
much
sense.
The
whole
point
is
that
the
tenant
administrator
explicitly
in
any
opposed
to
site
collection,
scoped,
app
catalog,
for
example,
in
a
subset
of
site
collections
or
in
one
site
collection.
A
The
scenario
would
be
something
like
hey:
we
have
a
global
intranet
plus
we
have
tens
of
thousands
of
collaboration
sites
and
we
want
to
actually
have
a
subset
of
add-ins
or
SharePoint
framework
solutions
available
in
that
global
intranet
site
collection,
but
not
available
in
the
collaboration
sites
or,
alternatively,
what?
If
you
want
to
test
and
pilot
some
of
your
upcoming
capabilities
in
a
subset
of
site
collections,
but
not
across
the
whole
tenor?
So
you
can
use
the
site
collection,
scope,
app
catalog
for
that
and
the
tenant
administrator
has
to
enable
this
capability.
A
So
there's
still
the
covenants
level
layer
said
administrative
layer
and
whoever
owns
the
tenon
will
enable
that
capability
in
a
site,
collection
level
and
at
that
point
the
site
collection
administrator,
can
then
start
installing
and
adding
capabilities
and
this
app
catalogues
inside
collection
level,
which
will
then
make
sure
that
you're
able
to
install
then
in
the
inside
of
that
site,
collection
and
sub
sites
and
everything
else.
So
it
is
really
for
add-ins
and
its
last
apps,
whatever
you
want
to
call
them
and
also
for
SharePoint
framework
solution.
B
Yeah
yeah,
so
because,
when
I
think
about
it,
it's
might
be
for
some
hard
to
understand
why
what's
exactly
the
benefit
right?
So
in
the
past,
when
you
would
deploy
either
add
an
RSP
effects,
catalog
in
your
tenant,
what
you
would
get
is
like
with
add-ins
you
had
two
options:
you
would
deploy
it
to
your
sites
and
then
make
it
available
in
all
size
to
be
installed
right.
So
you
would
go
to
every
single
site
that
you
want
to,
and
you
would
say
at
an
app
and
at
that
poor.
B
At
that
point
you
would
actually
install
the
add-in
in
your
site
or
with
add-ins.
You
had
also
the
option
that
to
install
it
globally
in
all
sides,
and
then
you
would
install
it
actually
in
the
App
Catalog
side
and
then
it
would
be
already
available
in
all
sides.
Correct
correct.
That
is
correct,
with
SPF
X
there's
similar
approach,
because
we
can
go
to
the
App
Catalog
tenant
or
the
tenant
app
catalog.
B
When
we
you,
when,
when
we
add
the
package
there
and
deploy
it,
we
can
then
add
it
to
all
side
or
we
can
use
the
tenant
sculptor
deployment
and
then
everything
becomes
available
across
all
sides
correct.
So
what
is
the
benefit
here
right,
so
the
benefit
here
is
that
not
everybody
will
have
the
option
to
actually
install
the
or
add
the
add
in
in
the
site
correct.
That
option
will
not
be
available
to
everybody
where
it
is
available.
If
you
use
the
tenant
app
a
lot
correct,
correct.
A
Yes,
so
so
let
me
kind
of
a
refresh
this
one.
So
if
you
think
about,
let's
think
about
this
from
a
SharePoint
framework
solution
perspective
only
so
with
the
SharePoint
framework
solution,
you
have
the
tenant
scope
deployment
option,
which
means
that
the
solution,
although
the
web
part
as
an
example,
is
immediately
available
across
the
tenant.
So
this
is
not
designed
for
them
and
that
the
site-specific
app
catalog
is
not
designed
for
tenant
scope,
deployment
option
and
what
is
really
almost
technically
there's
nuances
behind
of
that
statement.
But
let's
not
actually
vary
about
that.
A
Technically.
This
is
designed
for
the
scenario
where
your
SharePoint
framework
solution
is
designed
to
be
installed
explicitly
on
a
slide,
and
it
might
do
some
feature
framework
provisioning
on
a
site
or
a
new.
You
want
to
target
the
functionality
to
be
available
only
when
it's
actually
getting
installed
and
if
you
ain't
user
goes
to
add
an
app
on
a
site.
What's
getting
visible,
there
is
dependent
on
those
add-ins
which
are
in
turn
that
catalog.
So
using
this
one.
B
So
there's
actually
on
this
yeah
exactly
exactly
right.
So,
in
other
words,
if
you
want
your
thing
where
an
add-on
or
SP
effects
pollution
that
that
you've
built
to
be
available
only
in
specific
site
collections,
this
is
exactly
what
you
new
need
correct.
You
have
to
deploy
it
to
the
app
catalog
site,
collection,
app,
catalog
and
not
tenant,
one
correct
yes!
A
So
why
is
this
important?
We
kind
of
went
through
a
lot
of
these
things
already
in
there
in
the
previous
line
as
well,
but
this
is
really
around
providing
the
flexibility
for
in
the
process
under
deployment
options
and
the
site
collection
scope
at
catalog
Gus
give
you
the
decentralized
management
of
the
add-ins
and
SPF
X
packages.
So
let's
say
a
classic
example
would
be
that
HR
or
whatever
business
organization
they
want
to
have
more
flexibility.
A
They
want
to
have
their
own
widgets
to
be
only
available
within
their
site
collection
and
and
they
they
don't
or
you
as
an
administrator.
You
do
not
want
to
get
let's
say,
be
the
bottleneck
of
them
getting
their
stuff
de
pointes,
so
you're
able
to
then
activate
the
site
collection,
scope,
catalog
for
them
to
manage
what
add-ins
are
being
available.
What's
your
plan,
ephemeral
solutions
are
being
available
within
that
site
collection.
A
The
second
dimension,
no
doubt
it's
the
scope,
deployment
of
having
a
sign,
shape,
one
framework
solution,
so
you're
able
to
target
those
solutions
to
be
available
only
in
a
subset
of
site
collections
and
that's
a
super
cool
capability.
Now
with
great
flexibility.
There's
obviously
increased
responsibilities
as
well,
which
we
always
need
to
remember
so
sure
this
provides
flexibility
for
enterprises
from
a
deployment
option
perspective
now,
at
the
same
time,
it
increases
the
risks
or
it
increases
the
the
requirement
of
training.
A
These
people
to
understand
want
us
to
add
in
actually
mean
what
does
the
SharePoint
framework
solution
mean
because
so
that
they
don't
accidentally
just
download
stuff
from
the
internet
and
start
putting
them
on
their
site
collection?
But
let's
not
actually,
let's
make
this
as
a
scary.
Scary,
no,
don't
do
this
discussion,
but
there
is
an
additional
layer
of
covenants
to
be
taken
into
account
whenever
you
enable
this
capability
in
your
site
collection.
So
the
people
who
manage
that
site
collections
go
grab
catalogs.
B
A
B
That's
not
not
not
the
case,
because
whatever
scripts
are
running
on
a
page,
they
run
as
a
part
of
the
page.
So
these
so
even
you
deploy
your
so
your
solution.
Only
to
one
side,
script
from
that
side
can
access
on
your.
We
have
the
whole
Internet
sure
right.
So,
that's
why
it's
so
important
that
you
verify
what's
inside
the
package
and
if
it's
okay
to
run
it
yeah,
because
there
is
no
way
for
you
to
isolate
it.
Only
to
that
one
side,
absolutely
absolutely.
A
And
and
one
kind
of
additional
thing
which
we
also
mentioned
on
the
previous
line-
but
this
is
this-
is
super
powerful,
also
that
the
site
collection
of
catalogs
is
super
powerful.
For
let's
say
you
want
to
do
piloting
you
want,
or
you
wanna
test,
your
let's
say,
upcoming
capabilities,
SharePoint
framework
solutions
in
production
environment
without
actually
releasing
them
to
be
available
for
your
end
users.
So
you
can
actually
then
create
a
separate
site
collection.
A
Where
you
do
the
pilot
pilots
of
your
solutions,
you
can
test
them
in
the
production
units
within
the
context
of
production,
tenon
and
then,
after
the
after
they've
been
signed
off,
you
can
put
them
in
the
app
catalog.
So
it's
a
great
it's
one
way
of
improving
or
one
great
improvement
actually
for
the
ALM
process
as
well.
Yep.
B
A
How
about
we
see
it
in
practice?
How
works?
Let's
actually
have
a
look
on
this
one
in
practice,
so
let's
jump
on
a
desktop
and
have
a
look
on.
How
do
we
actually
enable
and
the
site
collection
app
catalog
in
practice?
So
what
what
are
the
power?
And
how
do
we
do
that?
What
does
it
then
actually
mean
and
how
the
visibility
of
the
adding
is
dependent
where
it's
actually
getting
deployed?
A
Okay,
so
let's
have
a
look
on
how
we
enable
the
site,
collection,
site,
site
collection
at
catalog
and
and
the
scope
deployment
of
a
random,
adding
or
in
this
case,
SharePoint
framework
solution.
So
this
is
my
site
we're
going
to
use
in
my
development
tenant
or
in
my
example
tenon,
and
what
we
need
to
do
first
of
all
is
connect.
A
The
admin
are
using
the
SharePoint
on
my
management
cell,
so
in
my
case,
I've
already
done
that
so
I
can
do
a
get
SPO
tenant
and
you
can
actually
see
that
I'm
already
connected
to
my
tenor,
so
we're
using
the
shipment
on
my
management
shell
to
actually
enable
the
site
collection
of
catalog
in
that
particular
site
collection,
and
this
is
essentially
due
to
the
fact
that
you
need
to
have
still
the
tenant
admin
permissions
and
then
intact
in
control
to
be
able
to
do
so.
So
now.
A
Let's
actually,
then
enable
that
in
this
site,
collection
and
just
to
show
you
how
it's
actually
being
visible,
nothing
available
in
the
site,
collection
for
time
being-
and
it's
actually
getting
here
and
at
SPL
site
collection,
app
catalog,
and
then
we
can
provide
a
URL
to
the
site.
You
can
actually
provide
that
without
it
switch
as
well.
A
So
let
me
get
in
here
and
copy
that
one
and
paste
that
one
in
and
press
Enter
and
that's
gonna
then
execute
that
if
we
go
here,
we
don't
exactly
immediately
see
and
the
library
or
the
app
catalog
being
present.
So
this
takes
few
seconds
and
the
reason
that
that
one
is
that
what
actually
happens
is
that
there's
a
feature
getting
activated
in
the
site:
collection
which
is
secured.
A
A
Poem
works
both
in
modern
classic
site.
That
is
correct,
so
there's
no
difference
on
the
experience
from
that
perspective.
So
now
this
is
exactly
the
same
catalog.
What
you
have
in
the
app
catalog
in
the
tenant,
app
catalog,
so
the
behavior
and
functionalities
are
exactly
the
same.
So
how
would
we
then
use
this
or
how
would
we
actually
get
stuff
deployed
on
the
side?
So
let's
have
a
quick
look
on
that
so
I
have
here
an
example.
A
A
Do
the
the
shipping
at
the
production
deployment
so
to
say
for
this
for
this
particular
solution.
So
let's
make
that
one
happen.
It's
actually
slightly
not
just
that
one
picker
and
let's
also
do
call
up
package
lucien
ship,
so
we
actually
get
the
solution
I
created
underneath
the
SharePoint
folder
and
after
that
hasn't
has
been
done,
and
we
can
then
get
the
Dex
borer
and
open
up
this
folder
and
solution
structure
in
the
file
explorer
and
in
the
solution
folder.
A
We
now
have
two
SP
pkg
package,
so
let's
actually
do
this
side-by-side
there
we
go
and
there's
my
solution
and
let's
actually
try
contractor
from
him
and,
as
you
can
see,
all
of
the
basic
behaviors
are
working
as
well
in
this.
In
my
case,
I
didn't
update
actually
the
URLs
at
all,
so
essentially
it
is
still
showing
the
path
to
CDN
for
the
demonstration
of
purposes.
I
think
this
is
fine,
because
we're
not
gonna
actually
use
the
solution
or
the
web
part
it's
just
matter
of
showing
how
it's
visible
to
be
installed.
A
So,
but,
as
you
can
see,
that's
that's
really.
The
reason
I
didn't
update
the
configuration
of
my
solution
before
I
packaged,
and
so
we
can
do
deploy.
So
now
we
have
this
solution
available
within
this
site:
collection,
scope,
and
what
does
it
actually
mean?
Is
that
if
I
go
to
my
site
contents
in
the
site
collection,
where
we
actually
now
have
the
solution
installed?
So
let's
do
a
refresh
here
and
we
can
say
that
we
have
an
Apps
for
SharePoint.
A
We
have
one
item
installed
there
and
the
items
name
was
we
cast
app
catalog
client-side
solution.
So
now,
if
I
go
in
this
side,
collection
across
the
site,
collection,
multiple
sub
site
as
well,
and
if
I
can
add
an
app,
we
can
see
that
web
cast
app,
catalog,
client-side
solution
available
and
a
few
others
which
are
included
in
the
in
the
tenant
level
and
just
to
demonstrate
the
difference
in
here.
I
do
have
another
site
collection
here,
which
is
called
another.
So
now,
if
I
caught
the
site,
contents
I
don't
need
to
go
here.
A
A
good
good
could
have
clicked
at
an
app
directly
from
the
menu
as
well.
But
if
I
add
an
app
in
this
site,
collection.
I'm
always
saying
those
two
weights
are
coming
from
the
tenon
script,
so
essentially
in
the
one
where
we
have
the
site
collection,
scope,
app
catalog,
where
we
uploaded
this
to
the
SPP
KT
file
available.
We
can
see
that
additional
solution
to
be
available
and
to
be
installed
on
the
site
collection
will
make
sense.
A
Yes,
absolutely
that's!
That's
the
whole
idea,
so
we've
been.
We
chatted
around
that
one
in
slides
and
we'll
probably
do
that
in
the
summary
as
well
and
but
the
whole
point
is
that
you're
able
to
do
scoped
deployments
of
the
solution.
So
if
you,
the
classic
scenario,
is
no
doubt
I
have
a
global
intranet
and
I
want
to
have
a
specific
shape
and
framework
solutions
or
add-ins
only
available
for
cyclic
sites
and
in
that
site,
collection,
which
is
the
global,
Internet
or
subset
of
site
collections,
not
across
the
whole
tenor
and
create
capability.
A
Quite
simple
to
use
the
powershell
commandlets
is
as
simple
as
it
actually
gets
at
the
SPO
site.
Collection
of
catalog
can,
if
you're
able
to
add
that
one
there
and
obviously,
if
you
need
to
remove
that
you're
able
to
do
remove
s,
be
inside
collection,
app,
catalog
and
also
the
site
name
there
and
you're
able
to
get
that
capability
disabled
technically.
This
does
not
believe
the
app
catalog
it
essentially
just
disables
that
behavior
in
that
side
collection.
So
we're
not
deleting
anything
from
the
that
folder
and
that
life
automatically.
B
A
Will
be
disabled
because,
basically,
what
happens
here
is
that
USA
administrator
you're
saying
that
hey
in
this
site
collection
any
any
item
in
an
app
catalog.
It's
not
fine
to
be
executed,
so
the
manifest
is
no
longer
valid.
So
therefore,
the
individual
functionality
within
the
pages
is
no
longer
render.
So
it's
not
it's
not
an
exception.
It's
not
an
error.
It.
The
functionality
is
not
just
enabled
or
rendered
that
make
sense.
Yep,
cool,
I!
Think
that's
it.
A
So,
let's
flip
back
on
the
slides
and
and
do
a
quick
summary
on
on
what
we
went
through
in
this
webcast
cool
I.
Think
that's
it
for
this
one
relatively
simple
scenario
when
you
think
of
it,
but
it
does
enable
a
lot
of
lot
of
additional,
let's
say,
options
and
a
lot
of
additional
flexibility
again
for
the
enterprises
and
I
I,
really
like
the
fact
that
this
is
once
again.
This
is
the
from
simplicity
and
flexibility
for
enterprises.
A
So
if
you
choose
to
use
this
option,
it
will
enable
you
to
be
more
successful
or
it
will
enable
more
scenarios
within
your
SharePoint
or
antenna,
and
it's
a
relatively
simple
thing
to
enable
as
well.
So
you
only
need
to
have
that
powershell
commandlets
and
enable
that
in
a
specific
site,
collection
any
and
good
to
go,
you
are
falling
under
that
you're.
Still,
you
can
start
using
the
site
collections
that
catalogue.
Anything
else
wanted.
We
want
to
add
here.
I
want
I.
B
Believe
we
went
through
the
whole
thing:
it's
a
new
ability,
it's
a
new
feature
or
new
tool
that
we
have
available
in
our
tool
box
and,
as
you
said,
right,
it
improves
adoption.
It
allows
us
to
test
things
already
in
production
without
making
it
available
to
everybody
in
one
big
blast
and
it
also
frees
tenant
admins
from
approving
every
single
package
across
the
whole
internet.
Yes,
so
it's
a
big
big
improvement
on
management
of
your
our
tenant.
Absolutely.