1
00:00:01,306 --> 00:00:02,533
Welcome to Briard!

2
00:00:02,888 --> 00:00:07,710
If you manage compliance or security, you
probably spend a lot of time asking the

3
00:00:07,730 --> 00:00:08,918
same questions.

4
00:00:09,273 --> 00:00:11,384
Which AI tools are people using?

5
00:00:11,753 --> 00:00:13,047
Who is responsible?

6
00:00:13,402 --> 00:00:15,223
And what still needs a decision?

7
00:00:15,565 --> 00:00:18,231
Let's see how Briard brings that work
together.

8
00:00:18,586 --> 00:00:21,476
You don't need a technical background to
follow along.

9
00:00:21,831 --> 00:00:25,650
We're using a fictional company and sample
information throughout this

10
00:00:25,670 --> 00:00:26,739
demonstration.

11
00:00:27,094 --> 00:00:32,451
Here on Home, Jane sees one clear next
step: provide proof for an AI tool.

12
00:00:32,793 --> 00:00:37,205
The explanation tells her why it matters,
and the button takes her straight to the

13
00:00:37,225 --> 00:00:37,833
work.

14
00:00:38,175 --> 00:00:42,680
Start here each day, check the place you're
reviewing, and focus on the next

15
00:00:42,700 --> 00:00:43,756
useful action.

16
00:00:47,327 --> 00:00:49,637
First, let's open My AI tools.

17
00:00:49,979 --> 00:00:54,240
This is your shared list of the AI tools
your organization has recorded.

18
00:00:54,583 --> 00:00:57,011
Choose a tool on the left to see its
record.

19
00:00:57,353 --> 00:01:02,359
In this sample, we have tools used in a
secure project, the main work environment,

20
00:01:02,379 --> 00:01:04,015
and clinical operations.

21
00:01:04,370 --> 00:01:05,915
That context matters.

22
00:01:06,270 --> 00:01:10,577
A tool used for everyday office work may
need a different review from one used

23
00:01:10,597 --> 00:01:12,273
with sensitive information.

24
00:01:12,641 --> 00:01:15,795
The guided view keeps the next question
easy to find.

25
00:01:16,150 --> 00:01:19,159
When you need more detail, open See full
record.

26
00:01:19,501 --> 00:01:24,633
You can review the profile, answers,
supporting proof, and things still to fix.

27
00:01:24,988 --> 00:01:29,915
Your team has one place to return to,
instead of rebuilding the story from emails

28
00:01:29,935 --> 00:01:31,070
and spreadsheets.

29
00:01:34,641 --> 00:01:36,699
What if a tool isn't on the list yet?

30
00:01:37,055 --> 00:01:39,087
Open More, then Add an AI tool.

31
00:01:39,442 --> 00:01:42,477
We'll add a fictional Contract Review
Copilot.

32
00:01:42,819 --> 00:01:45,142
First, enter the name and provider.

33
00:01:45,484 --> 00:01:49,112
Next, explain its planned use in everyday
language.

34
00:01:49,494 --> 00:01:54,310
Here, it helps draft contract summaries,
and a person reviews the result.

35
00:01:54,665 --> 00:01:57,607
Then identify the kinds of information
involved.

36
00:01:57,963 --> 00:02:02,092
You don't need to paste in a contract or
share someone's private details.

37
00:02:02,434 --> 00:02:05,588
Finally, review the summary and create the
record.

38
00:02:05,943 --> 00:02:10,870
That's the starting point: a named tool, a
clear purpose, and a record your team

39
00:02:10,890 --> 00:02:12,170
can work on together.

40
00:02:12,526 --> 00:02:15,758
Adding the record doesn't automatically
approve the tool.

41
00:02:16,114 --> 00:02:19,096
It gives you a practical place to complete
the review.

42
00:02:22,670 --> 00:02:26,621
Invite your coworkers into the same
workspace so your team can share the tool

43
00:02:26,641 --> 00:02:28,858
records, answers, and proof.

44
00:02:29,200 --> 00:02:33,435
Open Account and settings, then choose
Manage under Members and roles.

45
00:02:33,777 --> 00:02:35,559
Jane is the workspace Owner.

46
00:02:35,888 --> 00:02:40,901
An Owner or Admin can invite a teammate
using their work email and the right role.

47
00:02:41,230 --> 00:02:45,524
Choose Admin for someone responsible for
workspace settings, Contributor for

48
00:02:45,544 --> 00:02:49,212
someone who adds work, or Viewer for
someone who reads.

49
00:02:49,554 --> 00:02:52,404
Briard creates a private seven-day
invitation.

50
00:02:52,746 --> 00:02:58,253
The invitation, email confirmation, and
join in this recording are simulated; no

51
00:02:58,273 --> 00:03:00,358
real email or account is created.

52
00:03:00,701 --> 00:03:05,279
The recipient uses the invited email and
signs in or creates their account.

53
00:03:05,621 --> 00:03:08,709
Their refreshed session opens the invited
workspace.

54
00:03:09,064 --> 00:03:14,420
Back in the member list, the team shares
one workspace, with each person's role
visible.

55
00:03:14,762 --> 00:03:19,393
To change a joined member's access, select
their new role and choose Save role.

56
00:03:19,722 --> 00:03:22,348
Removing a member requires confirmation.

57
00:03:22,690 --> 00:03:25,607
Owner access and your own access stay
protected.

58
00:03:25,949 --> 00:03:30,857
Owners and Admins also need an
authenticator code to protect workspace
management.

59
00:03:31,199 --> 00:03:35,769
Keep a responsible administrator in place,
and give each person the access their

60
00:03:35,789 --> 00:03:36,911
work requires.

61
00:03:40,457 --> 00:03:42,885
A saved answer states what your team knows.

62
00:03:43,189 --> 00:03:45,854
Supporting material lets a reviewer check
it.

63
00:03:46,195 --> 00:03:51,024
Here, Microsoft 365 Copilot is an internal
productivity pilot.

64
00:03:51,366 --> 00:03:55,364
This fictional purpose and allowed-use
brief supports that purpose answer.

65
00:03:55,693 --> 00:03:57,580
Open What can I use as proof.

66
00:03:57,909 --> 00:04:01,722
A purpose record explains the job, provider
and setup.

67
00:04:02,064 --> 00:04:06,709
Data and safeguard records explain
permitted information and required checks.

68
00:04:07,064 --> 00:04:10,917
Completed test or approval records show
what was checked or decided.

69
00:04:11,259 --> 00:04:14,755
Include the tool, workplace, owner, current
version and dates.

70
00:04:15,084 --> 00:04:17,578
From the question, choose Add a file
instead.

71
00:04:17,907 --> 00:04:23,475
Check Proof supports, set when this
material needs another review, and select
the file.

72
00:04:23,817 --> 00:04:26,865
Use an approved file type within the
displayed limit.

73
00:04:27,194 --> 00:04:30,176
Choose Add and check proof, then check the
result.

74
00:04:30,505 --> 00:04:34,133
Scan passed means the file passed safety
and integrity checks.

75
00:04:34,475 --> 00:04:37,695
It does not prove the answer is correct or
approve the tool.

76
00:04:38,037 --> 00:04:41,256
This recording uses a simulated upload and
scan.

77
00:04:41,598 --> 00:04:46,374
A separate review procedure supports
whether a person must check important AI
work.

78
00:04:46,717 --> 00:04:51,796
An approved HTTPS link is another option
when a reviewer can access its source.

79
00:04:52,138 --> 00:04:54,368
Match each item to its own question.

80
00:04:54,711 --> 00:04:57,943
Use approved, non-regulated material only.

81
00:04:58,285 --> 00:05:03,141
Keep real customer records, regulated data,
passwords, prompts and outputs out.

82
00:05:03,483 --> 00:05:08,707
If a fact or its support is uncertain, keep
it open for the person who can confirm it.

83
00:05:12,237 --> 00:05:14,824
You can also reduce some of the manual
work.

84
00:05:15,166 --> 00:05:19,678
Open Shadow AI Discovery, then select the
workplace you're reviewing.

85
00:05:20,020 --> 00:05:24,538
The source areas show the different places
AI can appear, from work accounts to

86
00:05:24,558 --> 00:05:28,226
devices, cloud services, and employee
reports.

87
00:05:28,568 --> 00:05:31,920
We'll choose Work accounts and Microsoft
365.

88
00:05:32,275 --> 00:05:34,861
Each check has its own access and coverage.

89
00:05:35,203 --> 00:05:38,713
Here, the fictional workspace already has
an approved account.

90
00:05:39,042 --> 00:05:41,905
Review What access does this use before
starting.

91
00:05:42,247 --> 00:05:47,135
The connection and result in this recording
are simulated; no customer account or

92
00:05:47,155 --> 00:05:48,817
provider is contacted.

93
00:05:49,160 --> 00:05:53,928
In your workspace, wait for a completed
check and review its scope, last-success

94
00:05:53,948 --> 00:05:55,505
time, and limitations.

95
00:05:55,821 --> 00:05:58,869
Saving a connection alone does not mean it
was checked.

96
00:05:59,211 --> 00:06:00,637
Now review a finding.

97
00:06:00,979 --> 00:06:04,964
Look at its source, confidence, and what
the evidence cannot establish.

98
00:06:05,266 --> 00:06:08,367
Choose Yes, this is ours, No, not ours, or
I'm not sure.

99
00:06:08,709 --> 00:06:10,517
Uncertainty stays visible.

100
00:06:10,859 --> 00:06:15,345
After confirmation, Add to AI inventory
creates a governed record.

101
00:06:15,687 --> 00:06:20,107
Your team still supplies the owner,
purpose, and permitted information.

102
00:06:20,449 --> 00:06:24,183
A finding doesn't approve an AI tool or
create a KAIDAN case.

103
00:06:24,525 --> 00:06:28,990
Keep unchecked sources visible as gaps, and
add anything the approved sources

104
00:06:29,010 --> 00:06:29,948
cannot see.

105
00:06:30,290 --> 00:06:34,768
When separately enabled for your workspace,
Device and model inventory shows

106
00:06:34,788 --> 00:06:37,730
reported computers and their apps or
models.

107
00:06:38,073 --> 00:06:42,709
This expanded workflow is off by default
and still needs approved sources and

108
00:06:42,729 --> 00:06:44,075
rollout validation.

109
00:06:44,418 --> 00:06:48,283
Installation or a model being available
does not prove it was used.

110
00:06:48,626 --> 00:06:53,679
Check fleet coverage compares completed
checks with an approved expected-device
register.

111
00:06:54,021 --> 00:06:59,034
Here, the percentage stays unknown because
that expected set hasn't been confirmed.

112
00:06:59,363 --> 00:07:03,981
Review the source's inventory date, missing
checks, and identity gaps.

113
00:07:04,323 --> 00:07:08,967
Downloading a signed collector is not the
same as installing it or completing a
check.

114
00:07:09,309 --> 00:07:12,226
Your administrator approves that setup
separately.

115
00:07:15,784 --> 00:07:20,156
Once the records are in place, What needs
me helps you decide where to spend your

116
00:07:20,176 --> 00:07:20,744
time.

117
00:07:21,086 --> 00:07:25,625
Choose the part of the organization you're
reviewing, then read the next action

118
00:07:25,703 --> 00:07:27,102
and its explanation.

119
00:07:27,458 --> 00:07:30,849
You don't have to work through every detail
on every visit.

120
00:07:31,191 --> 00:07:35,524
Start with the item that needs a person,
follow the button, and bring back the

121
00:07:35,544 --> 00:07:37,589
answer or evidence that's missing.

122
00:07:37,945 --> 00:07:42,463
This is especially helpful when you're new
to the platform: the next step is

123
00:07:42,483 --> 00:07:44,673
connected to the record it belongs to.

124
00:07:45,028 --> 00:07:49,652
Briard helps organize the follow-through,
while your team stays responsible for

125
00:07:49,672 --> 00:07:50,702
the decisions.

126
00:07:54,303 --> 00:07:56,599
Next, let's open My AI policy.

127
00:07:56,942 --> 00:08:01,269
This brings policy work into the same
workspace as your AI records.

128
00:08:01,624 --> 00:08:05,372
At the top, you can see the draft's status
and the next action.

129
00:08:05,714 --> 00:08:09,546
Review my answers takes you through
straightforward questions, such as the

130
00:08:09,566 --> 00:08:14,769
organization name, who owns the policy, and
what information employees must not

131
00:08:14,789 --> 00:08:16,254
put into an AI tool.

132
00:08:16,623 --> 00:08:21,557
The draft is organized into sections, so
you can review one topic at a time.

133
00:08:21,913 --> 00:08:26,549
Here are the rules for acceptable and
prohibited use, followed by a short
employee

134
00:08:26,569 --> 00:08:27,164
guide.

135
00:08:27,519 --> 00:08:32,071
That makes the policy easier to discuss
with the people who will actually use it.

136
00:08:32,413 --> 00:08:34,551
You can also set a review schedule.

137
00:08:34,906 --> 00:08:39,622
The aim is a policy your team can maintain,
rather than a document that's written

138
00:08:39,642 --> 00:08:40,975
once and forgotten.

139
00:08:44,570 --> 00:08:46,405
A draft is only the beginning.

140
00:08:46,747 --> 00:08:50,948
Approve and publish shows who needs to
review the policy before it becomes the

141
00:08:50,968 --> 00:08:52,051
approved version.

142
00:08:52,393 --> 00:08:57,485
In a signed-in workspace, you choose
eligible reviewers and the required roles.

143
00:08:57,828 --> 00:09:00,559
This sample doesn't send approval requests.

144
00:09:00,914 --> 00:09:05,181
Keeping the draft and published version
separate lets your team work on changes

145
00:09:05,201 --> 00:09:08,144
while the current approved policy remains
in place.

146
00:09:08,486 --> 00:09:13,254
Share and track is the next stage, where
the approved policy can be distributed

147
00:09:13,274 --> 00:09:15,003
and acknowledgments recorded.

148
00:09:15,359 --> 00:09:19,402
You can see who has responded without
treating a response as proof that someone

149
00:09:19,422 --> 00:09:20,728
has learned everything.

150
00:09:21,070 --> 00:09:26,564
For a compliance manager, the benefit is
visibility: what is being edited, what

151
00:09:26,584 --> 00:09:29,843
needs approval, and which version people
should be using.

152
00:09:33,451 --> 00:09:37,343
When someone asks for an update, open Make
a review package.

153
00:09:37,685 --> 00:09:43,015
Start with who it's for: a customer,
advisor, insurer, or your leadership team.

154
00:09:43,370 --> 00:09:47,711
We'll choose Leadership, select the
relevant AI tool, and make the package.

155
00:09:48,066 --> 00:09:52,829
The new executive package appears in the
recent list, with a download available.

156
00:09:53,171 --> 00:09:57,927
You're bringing recorded information
together for a specific review, rather than

157
00:09:57,947 --> 00:10:00,507
starting from an empty document each time.

158
00:10:00,849 --> 00:10:05,124
Check the package and any open items before
sharing it outside your team.

159
00:10:05,466 --> 00:10:10,102
A package helps organize the evidence; it
doesn't turn missing proof into

160
00:10:10,122 --> 00:10:10,809
approval.

161
00:10:11,164 --> 00:10:15,906
The same habit applies whenever a colleague
asks about a tool: open the current

162
00:10:15,926 --> 00:10:20,162
record, review what's supported, and share
the appropriate information.

163
00:10:23,737 --> 00:10:25,585
One quick note about alerts.

164
00:10:25,927 --> 00:10:31,355
Home shows active AI incident alerts by
review priority and category, with links

165
00:10:31,375 --> 00:10:32,273
into KAIDAN.

166
00:10:32,602 --> 00:10:34,621
P1 needs the fastest review.

167
00:10:34,963 --> 00:10:39,396
An alert means something needs checking; it
isn't proof that harm occurred.

168
00:10:39,725 --> 00:10:44,884
Review a selected alert, or open all KAIDAN
alerts through the protected handoff.

169
00:10:45,226 --> 00:10:48,881
A summary that cannot load is unavailable,
not zero.

170
00:10:49,223 --> 00:10:52,944
And no open alerts does not mean every AI
tool is monitored.

171
00:10:53,286 --> 00:10:55,437
Check the source coverage in KAIDAN.

172
00:10:55,779 --> 00:10:59,460
We'll cover the deeper investigation in its
separate walkthrough.

173
00:11:03,084 --> 00:11:06,105
You don't have to remember every step from
this video.

174
00:11:06,460 --> 00:11:11,255
Learn Briard provides short guided lessons
for common tasks, including adding a

175
00:11:11,275 --> 00:11:14,930
tool, answering questions, and preparing a
package.

176
00:11:15,272 --> 00:11:18,004
Open a lesson when you're ready to do that
work.

177
00:11:18,346 --> 00:11:23,346
The Help page also explains common
questions and gives you a route to support.

178
00:11:23,701 --> 00:11:27,844
In your signed-in workspace, you can ask
for help and follow your request.

179
00:11:28,186 --> 00:11:30,206
This sample won't send a message.

180
00:11:30,561 --> 00:11:35,640
If you're just getting started, keep your
first session small: record one AI tool,

181
00:11:35,890 --> 00:11:40,434
answer the first question, and identify the
person who can provide any missing

182
00:11:40,454 --> 00:11:41,036
proof.

183
00:11:41,378 --> 00:11:44,281
You can build from there as your team gets
comfortable.

184
00:11:47,866 --> 00:11:53,043
That's a practical first day with Briard:
see your AI tools, understand what needs

185
00:11:53,063 --> 00:11:57,765
attention, keep your policy current, and
prepare information for the people who

186
00:11:57,785 --> 00:11:58,907
need to review it.

187
00:11:59,263 --> 00:12:03,115
You don't need to become a technical
specialist to keep that work moving.

188
00:12:03,458 --> 00:12:04,461
Ready to begin?

189
00:12:04,816 --> 00:12:09,400
Visit briard dot A I and choose Start
thirty days free, or sign in to your

190
00:12:09,420 --> 00:12:10,872
existing workspace.

191
00:12:11,227 --> 00:12:15,257
If you'd like help choosing your first
steps, contact our team at support at

192
00:12:15,277 --> 00:12:17,045
briard dash A I dot app.

193
00:12:17,401 --> 00:12:21,332
Tell us what your team is trying to manage,
and we'll help you get started.

194
00:12:21,675 --> 00:12:24,670
Start with one tool and one clear next
action.