►
From YouTube: Microsoft Teams Provision Automation with ProvisionGenie
Description
In this 35-minute all audiences-focused demo, Luise Freese and Carmen Ysewijn – share their creation - The Canvas app that looks like a Microsoft Teams Native app that deliberately prompts a team owner through the entire Teams provisioning process. With support from Power Apps, Azure Logic Apps, Managed Identity, Dataverse (full), Graph, Deployment tools and Documentation Genie delivers a reliable, secure, informative, easy to deploy and truly enterprise ready solution. The presenters’ step through the configuration of a Team that’s provisioned by Logic Apps. This PnP Community demo is taken from the Microsoft Power Apps community call – November 2021, recorded on November 17, 2021.
Demo Presenters:
• Luise Freese | @LuiseFreese
• Carmen Ysewijn (Qubix) | @CarmenYsewijn
Supporting documents:
• Blog - ProvisionGenie - an open-source provisioning engine for Microsoft Teams | https://techcommunity.microsoft.com/t5/microsoft-365-pnp-blog/provisiongenie-an-open-source-provisioning-engine-for-microsoft/ba-p/2796434
• Documentation - ProvisionGenie | https://provisiongenie.com/
• Repo – ProvisionGenie | https://github.com/ProvisionGenie/ProvisionGenie
Stay connected:
• Twitter https://twitter.com/microsoft365dev
• YouTube https://aka.ms/m365pnp/videos
• Blogs https://aka.ms/m365pnp/community/blog
• Call attention to your great work by using #PowerAppsCC and #PnPWeekly on Twitter.
A
B
A
B
It's
red,
it's
red,
so
it's
red
right
now
and
today
we
are
going
to
talk
to
you
about
provision
genie,
and
we
want
to
start
with
explaining
why
we
built
this
thing
that
we
built
because,
as
we
mentioned,
a
lot
of
our
customers
were
asking
us
for
something
to
provision
teams
and
we
both
felt
that
the
out
of
the
box
featured
to
create
teams
like
create
an
empty
team
doesn't
really
fit.
Users
needs
because
they
usually
don't
know
what
you
can
do.
They
don't
know
that
you
can
have
additional
libraries.
B
They
don't
know
that
sharepoint
is
in
the
back
end
and
that
you
can
have
lists
and
all
of
these
cool
things
inside
of
your
team
and,
on
the
other
hand,
a
lot
of
provisioning
solutions,
work
with
templates
that
then
provision
a
certain
number
of
channels
with
names
and
then
maybe
a
list
somewhere
in
there
for
planning
or
whatever,
and
that
also
doesn't
fit
users
needs,
because
they
always
want
something.
That's
slightly
different.
B
Additionally,
people
can't
really
articulate
their
needs,
and
that
is
why
we
wanted
to
build
a
solution
where
we
blend
learning
with
the
actual
requesting
of
the
team.
So
we
explain
in
the
application
why
they
would
want
different
channels
why
they
would
want
an
extra
library
or
a
list
in
their
team,
and
that
is
how
provision
genie
started,
and
we
have
the
a
couple
of
concepts
that
we
want
to
share
with
you,
and
I
will
just
put
them
all
on
the
screen
yeah
and
bring
it
online.
A
I'm
a
power
app
and
my
developer
does
not
know
how
to
make
an
app
like
look
like
a
team's
native
app.
Then
users
won't
be
that
likely
to
adopt
the
app
and
they
will
feel
like.
There
is
some
kind
of
friction
in
between
of
their
experience
that
they
get
in
teams
and
they
are
a
power
up
that
we
want
to
use
them
in
teams.
So
we
built
this
application
using
the
team's
ui
toolkit.
A
So
that
is
a
framework
that
is
mostly
used
by
our
product
colleagues
and
shows
them
how
a
button
should
look
like
how
a
table
should
look
like.
So
how
are
the
ui
components
should
look
like,
but
usually
powerapps.
Don't
look
like
that.
We
just
like
applied
this
to
our
canvas
app
so
that
this
app
really
looks
and
feels
like
teams
native.
A
B
And
then,
for
the
back
end,
we
didn't
actually
go
with
a
power
platform
solution,
so
we
created
the
first
version.
Like
the
proof
of
concept.
Can
we
do
what
we
want
to
do?
We
did
that
in
power
automate,
but
then
for
the
actual
solution.
We
decided
to
go
for
azure
logic
apps,
which,
if
you're
familiar
with
power
automate,
you
can
do
azure
logic
apps
as
well.
It
should
not
be
you
shouldn't
be
afraid
of
it,
because
it's
the
same
ui.
B
It
just
has
some
extra
features,
and
those
extra
features
is
why
we
went
with
azure
logic
apps,
because
with
the
power
automate
cloud
flow,
that
flow
will
run
in
the
context
of
the
user.
That
is
triggering
that
flow,
so
either
the
user
that
created
it.
If
it's
like
an
automatic
trigger
or
the
user
that
actually
clicks
the
button,
which
is
not
what
we
want.
We
wanted
this
to
run
in
the
context
of
an
app
so
that
we
can.
B
B
You
have
a
lot
better
developer
experience
because
you
can
you
can
you
do
have
the
visual
designer,
but
you
also
have
a
code
view
so
that
you
can
tweak
little
things.
You
can
more
easily
copy
things
from
one
logic
up
to
another.
If
you
want
to
split
that
up
and
it's
a
lot
easier
to
monitor
than
a
cloud
flow,
which
is
why
we
went
with
azure
logic,
apps
yeah,.
A
Exactly
so,
and
next
thing
related
on
the
autologic
apps
is,
of
course,
we
need
a
way
to
authenticate
against
a
graph
api,
because
every
magic,
of
course
is
backed
up
by
graph,
but
we
did
not
feel
that
we
wanted
to
have
an
app
registration
because
an
app
registration,
it
forces
us
to
have
an
app
secret
or
a
certificate.
And
let
me
tell
you
if
there
is
a
secret.
A
A
This
is
not
really
a
superior
solution,
so
we
went
for
a
managed
identity,
so
managed
identity
is
a
way
for
everyone
who
is
not
aware
right
now
to
give
your
application
an
identity
in
the
cloud
so
that
you
can
authenticate
against
without
the
need
of
having
and
maintaining
and
rotating
keys
or
secrets
and
stuff.
And
so
all
of
our
calls
work
with
the
managed
identity
and
the
managed
identity
is
also
part
of
the
deployment
of
which
we'll
attack
just
like
a
little
bit
later.
A
B
And
then,
as
for
the
data,
we
did
go
with
dataverse.
Of
course
we
had
the
option
of
going
with
sharepoint,
which
we
also
did
for
our
first
proof
of
concept
very
quickly
set
up
a
sharepoint
list
or
a
couple
of
sharepoint
lists,
put
it
in
there
and
see
if,
if
it
works
with
the
cloudflow,
but
then
again
we
were
thinking
about
okay.
So
we
want
to
really
make
this
an
enterprise-ready
solution.
We
want
this
to
be
reliable.
B
We
want
it
to
work
well
with
the
canvas
app
and
that's
why
we
went
for
dataverse
because,
contrary
to
sharepoint,
which
is
not
a
relational
database
dataverse
is
we
can
have
role-based
access
control
with
the
security
rules
that
are
built
in
so
we
can
decide
which
which
requests
a
user
does
they
can
see?
Can
they
see
everything?
Can
they
only
see
their
own
or
the
ones
from
their
team?
You
can
decide
all
that
in
data
first,
so
you
have
a
lot
more
granular
control
over
what
people
can
see
the
same.
B
If
you
want
to
do
something
for
admins
later
on,
they
will
be
able
to
see
more
than
a
user
does,
and
maybe
they
can.
They
can
also
do
more
than
usual.
As
I
mentioned,
it's
a
relational
database
because
we
do
have
several
tables
that
we
are
storing
our
data
in
and
there
are
relationships
between
those
tables.
So
it
was
important
for
us
to
know
that
that
data
would
be
stored
well
and
it's
more
performant
when
you,
when
you
combine
it
with
a
canvas
app
because
it's
built
in
the
same
platform.
B
A
And,
of
course,
we
have
a
good
reason
to
not
just
like
do
the
little
sister,
the
intervals
for
teams,
because
so,
if
you
do
dataverse
for
teams,
then
your
dataverse
database
is
then
tied
to
the
lifecycle
of
the
team.
And
if
we
speak
about
this
very
organizational
context,
then
this
feels
wrong.
So
this
is
just
like
playing
wrong
to
do
that,
and
I
guess
this
is
more
a
question
of.
Can
I
just
like
work
around
the
additional
license
and
whenever
we
ask
ourselves
to
do
so,
we're
holding
this
wrong.
A
And
if
you
go
for
azure
logic
apps,
then
you
need
to
put
that
into
an
arm
template
and,
of
course,
the
solution
itself
is
the
zip
file
that
you
can
then
download.
But
we
have
an
entire
deployment
guide
to
make
sure
that
you
can
deploy
this
into
your
tenant
as
well,
and
we
have
right
now
we
could
announce
our
first
major
community
contribution
so
shout
out
to
gavin
barron
he's
not
only
a
dear
friend
but
who
worked
with
us
on
our
deployment
script
to
deploy
provision
genie.
A
So
first
we
had
manual
steps
to
deploy
the
solution
which
required
just
like
you
go
into
the
azure
portal
and
just
like
clicking
a
lot
of
buttons
until
you
were
at
the
point
where
all
azure
resources
were
ready
in
their
tenants,
so
that
you
could
actually
deploy
the
solution
from
our
template
files
and
he
automated
everything
with
us
together,
and
it's
really
a
major
step
forward
with
us.
So
thank
you
for
that
and
it
proves
the
power
of
open
source
and
community.
A
C
A
A
If
you
want
to
deploy
this
with
a
new
script,
if
you
know
what
you're
doing
under
five
minutes,
if
you
don't
know
what
you're
doing
it
will
take
about
half
an
hour,
because
you
first
need
to
educate
yourself
about
security
rules
which
are
also
part
of
the
process
or
application
user,
but
mostly
database
stuff.
But
if
you
know
what
you're
doing
it
takes
less
than
five
minutes
to
deploy
that
into
a
tenant.
C
B
Yeah,
so
what
we
still
wanted
to
talk
about
before
we
jump
into
the
actual
demo
is
the
documentation
that
we
created,
because,
as
louisa
mentioned,
this
is
an
open
source
solution
that
you
can
find
on
github,
and
we
also
have
a
website
it's
provision,
gme.com,
where
you
can
find
all
of
our
documentation.
So
we
haven't
just
uploaded
the
solution
to
github
and
then
written
a
quick
explanation
of
what
it
should
do.
We
have
created
in-depth
documentation
about
what
are
the
components?
Why
did
we
make
certain
decisions?
B
B
So
you
can
see
that
we
have
a
request
and
then
a
request
has
channels,
because
a
team
has
channels,
we
have
a
live.
We
can
have
libraries,
you
can
have
lists
and
of
course
you
can
have
multiple
of
these
as
well,
and
then
a
library
analyst
have
columns
in
them
so
that
you
can
also
link
all
of
that,
and
this
is
our
data
model
in
data
first,
as
it
is
now
as
the
solution
is
available,
but
this
can
be
easily
added
onto
like
we
are
doing.
B
We
are
working
on
members
now,
which
you
will
see
in
the
demo
that
we
are
about
to
give
as
well,
that
we
will
add
members
and
additional
owners
to
the
team
as
well,
which
then
creates
a
new
relationship,
and
this
is
why
data
first
is
was
for
us
the
way
to
go
because
relationships
when
you're
talking
about
teams.
If
you
do
that
in,
if
you
want
to
model
that
in
a
data
structure,
you
will
have
relationships
between
different
types
of
data.
A
Okay,
so
what
you
can
see
here
now
is
our
provision.
Genie
is
already
added
as
a
personal
app
to
your
teams.
It
has
a
beautiful
icon,
so
thanks
michael
for
doing
the
the
provision
genie
logo.
So
we
have
a
lot
of
shout
outs,
because
this
yet
again
is
a
community
effort
and
what
you
can
see
is
we
first
try
to
educate
our
users.
A
So
we
have
these
four
cards
and
we
thought
staying
on
track
of
everything
that
you
need
to
do
just
like
your
task
management,
so
that
people
would
not
confuse
now
chat
with
a
task
management
tool
and
say:
hey
carmen.
Could
you
please
do
this
or
that
and
then
by
chat,
so
because
that
is
not
better
than
doing
the
very
same
thing
by
email
and
uneducated
users
would
do
so
so
we
educate
them
and
tell
them
hey.
A
We
can't
go
for
a
managed
identity
and
then
we
need
to
have
a
workaround
with
a
messy
service
account.
And
then
this
can't
be
mfa
enabled-
and
this
feels
like
this
feels
messy
and
as
if
we
shouldn't
do
that,
and
this
is
why
we
chose
to
not
do
that,
but
provide
people
with
a
sharepoint
list
that
mimics
the
behavior
of
a
planner
plan,
just
like
has
all
the
different
columns
that
we
find
on
a
planner
task
and
educate
people.
How
to
do
this
and
we
heard
it
at
ignite.
A
Second
thing
that
we
educate
is
on
conversations
like.
Please
don't
start
every
time
in
your
conversation,
if
you
want
to
reply
to
what
our
ad
mentions
for
please
don't
overly
use
notifications
and
something
like
that,
so
we
educate
people
not
only
how
it
works,
but
what
are
some
very
good
practices
on
how
to
get
started,
because
yet
again,
usually
people
who
are
new
to
teams?
And
yes,
there
are
still
people
new
to
teams.
You
can't
believe
it.
They
can't
articulate
what
they
really
want.
A
Then
we
educate
about
having
better
meetings,
because
we
know
we
are
stuck
in
meetings
way
too
long,
so
they
take
too
much
time
and
then
there
is
no
time
left
for
the
actual
work
that
should
happen
just
like
in
between
of
the
meetings.
So
we
try
to
make
some
good
suggestions
on
how
to
really
excel
at
meetings
and
perhaps
just
like
not
attend
all
of
them
just
because
you
got
invited.
A
So
that
is
a
good
thing
and
we
educate
about
recordings
as
well
and
once
we
have
that
last
step
on
educating
users
and
comments,
closing
that
is
about
organizing
your
content,
and
this
is,
of
course,
all
the
documents
and
files
that
will
live
in
different
sharepoint
libraries.
So
we
introduce
that
concept
of.
A
Okay.
So
this
is
the
education
part
and,
as
you
can
also
see,
we
do
not
only
have
a
nice
navigation
and
a
main
part
in
this
app,
but
on
the
left
hand
no
on
the
right
hand
side.
So
that
is
what
I
struggle
always
with.
On
the
right
hand,
side
we
have
this
sides
bar,
and
the
sides
bar
tells
you
what
you
can
do
on
this
screen.
It's
just
like
the
how
to
use
this
screen
on
every
single
screen
and,
of
course,
on
this
welcome
screen.
A
If
we
talk
about
members,
then
we
provide
learning
material
on
just
like
what
is
the
role
of
a
member
or
what
should
I
do
as
an
owner
or
what
is
a
guest
and
provide
additional
links
and
videos
to
that,
so
that
our
user
can
educate
himself
or
herself
more
easily
but
blends
this
with
the
request
with
the
process
of
requesting
that
team,
so
that
it
is
more
like
a
combined
experience.
Instead
of
I
will
always
need
to
switch
context
again
and
again.
A
Okay,
so
shall
we
provision
a
team?
I
think
we
shall
yeah.
I
I
think
we
should
do
that.
So
carmen
is
starting
that
provisioning
process
and,
of
course,
the
very
first
thing
that
we
need
to
do
is
we
need
to
give
it
a
name,
and
this
would
be
provision
genie
demo,
and
we
give
this
team
a
nice
description
and
then
we
can
ask.
A
A
Second
thing
is:
do
we
does
our
user
want
to
have
that
list
for
their
tasks,
as
we
already
mentioned,
so
this
is
optional.
We
only
provision
that
if
our
user
indicates
that
they
want
to
have
this-
and
we
also
introduce
the
gallery
view
already
here,
so
that
they
know
what
they
get
okay.
So
thanks
for
closing
this
pop-up
again
and
once
we
have
this,
we
navigate
to
the
next
screen.
A
A
And,
let's
add
an
additional
owner
and
as
now
carmen
is
demoing
this
I'm
the
additional
owner
of
that
one,
and
perhaps
you
saw
that,
depending
on
what
is
already
selected,
we
we
were
just
like
a
display
or
not
display
certain
certain
buttons
to
just
like
guide
our
user.
What
they
can
do
right
now
and
now
it's
just
like
so
you
can
see.
A
Janik
is
already
a
member
and
now
carmen
tries
to
add
yannick
as
well
as
an
owner,
and
we
got
a
notification
with
a
notify
function
which
says
so
in
order
to
make
yannick
an
owner
of
that
team.
You
first
need
to
remove
him
from
the
members
gallery,
because
that
wouldn't
make
any
sense
if
he
was
both
a
member
and
an
owner
and
vice
versa.
So
if
she
now
would
like
to
add
again
as
an
owner,
she
would
get
an
error
as
well,
because
I
am
already
in
the
gallery
of
an
owner.
A
So
there's
an
error.
So
she
can't
proceed
with
that,
but
she
needs
to
delete
my
name
and
then
add
another
one
or
no
one
as
well,
and
you
can
see
in
the
sidebar.
So
the
details
will
give
you
detailed
information
just
like
going
through
the
steps
so
that
it
is
totally
clear
what
the
user
is
expected
to
do
right
now.
So
it
is
just
like
the
the
help,
but
that
is
not
hidden
but
super
obvious
for
our
users
and
if
they
need
just
like
additional
information
like
yeah.
A
But
what
is
the
difference
between
a
member
and
an
owner?
Now
we
give
them
additional
resources
and
tell
them
hey
if
you
want
to,
we
have
resources
for
you,
so
you
can
just
like
click
them
and
educate
yourself
and
then
just
like
continue
with
that
process,
and
of
course
this
opens
and
an
additional
tab,
and
it's
always
microsoft,
resources
or
resources
that
we
really
really
trust
to
to
educate
users.
A
And
we
would
like
to
create
some
channels-
and
perhaps
you
might
have
noticed
that
each
and
every
single
screen
already
contains
this
check
mark
yeah,
but
I
don't
want
that.
So
in
this
case
we
have.
I
don't
want
to
create
channels,
and
if
we
check
this,
we
can
proceed
to
the
next
screen
already.
So
this
is
a
new
feature
which
we
implemented
right
now,
so
there
should
be
a
warning.
So
what
should
happen
with
the
channels
that
you
already
put
in
there
but
yeah?
So
it
is
work
in
progress.
A
So
under
the
encryption
it
is
under
construction.
Yes,
so
you
can
see
the
preview
here
of
the
next
release,
so
that
is,
that
is
not
anymore,
the
first
release,
but
that
is
already
yeah
in
progress
for
the
next
release.
So
we
review
our
channels
and
perhaps
carmen
made
a
mistake,
and
perhaps
we
want
to
delete
the
channel
again,
so
we
can
just
like
re-add
this,
so
there's
nothing
just
like
written
in
stone
and
our
user
is
always
staying
in
control.
What
happens
here
proceeding
here?
A
A
So
we
would
just
like
create
this
option
sets
and
after
that
we
will
go
ahead
and
save
this
library
as
well
and
yeah.
We
gotta
pop
up
because
it's
always
good
to
just
like
motivate
your
users
and
tell
them
hey
you're,
doing
things
right
so
that
they
stay
in
this
process,
and
now
we
do
pretty
much
the
very
same
thing
and
provision
a
list.
So
you
might
know
it
is
basically
the
same
thing.
A
A
So
I
can
still
review
that
and
go
back.
If
I
made
a
mistake,
then
I
will
review
my
channels
and
even
those
are
here
and
then
I
will
review
my
library
and
my
list
and
I
will
get
the
column
the
column
names
here,
so
that
I
can
review
that
as
well.
And
I'm
still
sure
yes,
I'm
exactly
doing
what
I
wanted
to
have
and
then
it's
time
to
check
out.
Which
means
I
need
to
select
this
checkbox
and
check
this.
A
And
only
then
this
final
submit
button
will
be
not
be
disabled
anymore,
but
we'll
be
in
edit
mode,
so
that
I
can
submit
the
data,
and
this
will
patch
all
the
stuff
that
you
saw
before
into
the
respecting
data
verse
tables
and
from
there
on
our
logic.
Apps
will
pick
up
those
values
and
will
provision
all
the
assets
that
our
user
requested
in
the
canvasser.
B
Yes,
so,
as
louise
mentioned,
the
logic
apps
patches,
the
the
canvas
up,
sorry
patches
the
data
into
dataverse
and
then
that
will
trigger
our
logic,
apps
and
yes,
we
have
multiple,
because
we
decided
that
we
wanted
to
be
able
to
have
components
and
that
it
was
easy
for
us
and
for
potentially
other
people,
since
we
were
going
to
open
source
it
to
reuse,
some
of
the
components
that
we
had.
So
that
is
why
we
have
one
main
logic:
app
which
takes
care
of
the
logic
of
actually
provision
genie.
B
So
it
takes
the
data
from
dataverse.
It
puts
that
into
a
certain
a
certain
format,
and
then
it
provides
that
to
each
of
the
child
logic
apps,
which
then
take
care
of
the
actual
doing
things.
So
we
have
for
each
of
the
things
that
we
are
doing.
We
are
adding
people,
we
are
creating
a
library,
we
are
creating
a
list.
We
can
create
a
task
list
which
then
in
turn
calls
the
create
list
flow
again,
because
this,
of
course,
has
the
the
calls
to
graph
to
create
an
actual
list.
B
We
have
one
that
starts
to
create
a
team
and
we
also
have
one
that
provisions
the
welcome
package
and
the
main
flow
takes
care
of
orchestrating.
All
of
that.
So
if
we
have
take
a
look
at
the
designer,
you
will
see
that
this
looks
almost
exactly
alike
to
power
automate.
So
if
you
can
do
that,
you
can
do
this.
That
is
the
same
journey
that
I
went
through
when
I'm
starting
with
provision
genie
and
the
logic
apps
will
kick
off.
When
a
record
is
created
in
dataverse,
then
we
will
initialize.
B
Some
variables
do
a
couple
of
things
in
the
background
and
then
we
are
going
to
make
everything
ready
to
create
the
team.
So
we
are
going
to
look
at
what
are
the
channels
that
we
have
and
then
we
will
put
that
into
a
certain
format
and
we
will
provide
that
to
our
child
logic
app,
which
will
actually
take
care
of
creating
the
team.
B
Let's
take
a
look
quickly
at
the
create
team,
because
I
believe
that
we
are
running
out
of
time.
So
let's
take
a
quick
look.
What
does
the
create
team
logic
app?
Do
it
does
not
have
any
link
to
dataverse,
so
it
can
be
reused
for
anything
else
that
you
want
to
reuse
it
for
as
well
as
long
as
you
provide
the
information
in
the
right
input
format.
B
It
will
first
create
a
group
for
the
team
because
we
are
starting
from
a
group
and
then
teamifying
that
group,
so
we
create
the
group.
Then
we
create
the
team,
so
the
teamification
process
of
that
group,
and
then
we
will
configure
the
channels
very
important
when
we
configure
the
channels
two
things.
We
make
sure
that
we
hit
the
files
endpoint
so
that
our
users
don't
get
this
annoying
error.
B
Your
files
aren't
ready
yet
when
they
first
open
the
team,
so
we
make
sure
that
that
files
folder
gets
provisioned
and
we
get
rid
of
the
wiki,
because
we
don't
like
the
wiki,
it's
not
reliable
if
it.
If
someone
accidentally
deletes
it,
it
it's
deleted
for
real
and
you
cannot
get
it
back.
We
want
to
prevent
our
users
from
accidentally
get
losing
their
data,
so
we
don't
want
the
wiki
tap.
We
delete
the
wikitap
for
every
channel
that
we
provision.
B
If
you
want
to
contribute,
you
can
find
the
link
to
github.
We
love
contributions,
because
we
cannot
do
this
on
our
own.
We
have
had
help
up
to
this
point
as
well
from
gavin,
but
also
from
michael
with
the
design
from
yannick
with
the
debugging.
So
if
you
want
to
contribute
as
well,
we
highly
welcome
it.
C
B
Because
the
team's
end
point
the
way
that
is
set
up,
you
first
need
to
provision
the
group.
You
need
to
wait
for
that
to
be
completed
and
then
for
the
teamification
to
happen,
but
it
has
been
created.
It's
the
second
one.
This
is
the
one
that
I
did
earlier,
but
it
has
been
created
in
the
meantime.
So
we
have
our
channels
that
we
provided.
B
C
B
One
of
the
things
that
is
on
the
roadmap
is
to
make
sure
that
these
get
pinned
in
one
of
the
channels,
because
for
now
they
are
in
the
sharepoint
site
in
the
background,
which
is
not
ideal.
But
that's
something
that
we're
that
we
want
to
do
in.
A
next
release
is
to
ask
the
user
also
which
channel
each
of
those
libraries
and
this
should
be
pinned
to
so
that
they
can
access
it
from
teams
immediately
as
well.
C
C
Thank
you
for
the
awesome
demo.
This
is
amazing,
youtube
put
so
much
time
and
effort
into
this,
not
just
in
making
it
and
building
it,
but
the
whole
website
how
we
built
it.
Everything
that
is
just
awesome.
Thank
you
so
much.
I
bet
we
could
do
a
deep
dive
on
it
for
an
hour
with
you
easily
so
much
you
built.
Thank.