Credential · IT and admins · 8 clock hours
AI Workspace AdministratorSet it up. Lock it down. Run it.
The person who runs your systems learns to run your AI: sign-in and data settings, company knowledge connected without oversharing, a pilot with support, and a monthly routine.
Hands-on in your company's own admin console: Microsoft 365 Copilot, ChatGPT Business or Enterprise, Gemini in Google Workspace, or Claude Team or Enterprise
The credential at a glance
- Credential
- AI Workspace Administrator Certificate
- Type
- Certificate
- Clock hours
- 8
- Format
- Four 2-hour build sessions, in person
- Schedule
- One 2-hour session a week, or two 4-hour half-days a week apart
- Price
- $1,000 a seat, invoiced after the last session
- Class size
- 8 to 15 people
- Assessment
- Rubric on the work itself, a live demo and a 20-question quiz
- Platform editions
- 4 platform editions. Every edition earns the same AI Workspace Administrator Certificate, to the same rubric. Only the admin console changes.
- TechCred
- Listing in progress. Reimbursement isn't guaranteed until the state lists it.
- Issued by
- Paglow Automations (Ohio AI Solutions LLC), Lima, Ohio
- Before the first session
- Runs the company's Microsoft 365 or Google Workspace, or will run its AI tools.
- Admin access to the company's AI business plan, or a trial or pilot workspace set up for class.
- A pilot group of three to ten coworkers the learner can set up.
- The company's AI-use policy, or a draft of one. The AI Policy & Governance workshop produces one.
What a holder can do
TechCred pays for applied skills in developing, building, configuring or operating technology. Every competency below ends in something the learner built, configured or ran, and an assessor checks the evidence.
Build
Make the thing that does the work.
Write a support runbook and an incident procedure for a data mistake, and run a drill of it.
Evidence: Runbook and drill record
Configure
Set the rules it runs under.
Configure sign-in, multi-factor authentication, user provisioning and offboarding for the AI workspace.
Evidence: Identity settings record
Configure data controls: retention, model-training opt-outs, sharing defaults, external sharing and logging.
Evidence: Data settings record with screenshots
Connect company knowledge (files, mail, calendars or sites) to the AI with the least access each use needs.
Evidence: Connector configuration
Set the rules for which assistants, agents, skills, plugins and connectors people may build, share or install.
Evidence: App and agent rules, in the console and in writing
Operate
Run it, test it, keep it running.
Audit file and site permissions for oversharing before any company knowledge is connected, and fix what the audit finds.
Evidence: Permissions audit and fixes
Run a pilot: set up a group, brief them on the rules, and collect usage and feedback.
Evidence: Pilot plan and usage report
Operate the workspace month to month: review usage and audit logs, check settings against the AI policy, onboard and offboard.
Evidence: Monthly checklist, completed once
Analyze
Measure the work before and after.
Inventory how AI is already used in the company, personal accounts included, and record the risks each use carries.
Evidence: AI use inventory
Two hours each. Something built every time.
In person, on the schedule that suits your team. Each session ends with something the learner keeps and the assessor checks.
Session 1 · 2 hours
Plan it, lock it down
The workspace's sign-in and data settings decided, applied and recorded.
- An inventory of how people already use AI, personal accounts included
- Sign-in, multi-factor and provisioning set for the workspace
- Data settings: retention, training opt-outs, sharing and logging
- A configuration record with screenshots
Proof: Inventory and configuration record
Session 2 · 2 hours
Connect knowledge safely
Company knowledge connected only where the permissions are right.
- A permissions audit for oversharing in files and sites
- Fixes for what the audit found
- Connectors to files, mail, calendars or sites, least access first
- Rules for which assistants, agents, skills, plugins and connectors people may build or install
Proof: Permissions audit, connector settings and app rules
Session 3 · 2 hours
Pilot and support
A pilot group running, with support and an incident plan.
- A pilot group set up and briefed on the rules
- Usage and feedback collection
- A support runbook: access requests, common problems, who to call
- An incident procedure for a data mistake, rehearsed in a drill
Proof: Pilot plan, runbook and drill record
Session 4 · 2 hours
Run it
A workspace the learner can run month to month.
- The monthly checklist: usage, audit logs, settings against the AI policy
- Onboarding and offboarding steps
- A pilot report with what to change before company-wide rollout
- A five-minute demo and the quiz
Proof: Monthly checklist, pilot report, demo and quiz
Weekly, or two half-days.
Same four sessions, same 8 clock hours, same credential either way. I don't run it as one long day: the week between visits is when people put what they built to work on real tasks.
Weekly
4 visitsOne 2-hour session a week for four weeks.
Between sessions, people use what they just built on real work, and the next session picks it up.
Two half-days
2 visitsTwo 4-hour half-days a week apart: sessions 1 and 2 on the first, 3 and 4 on the second, with a short break in each.
Between the half-days
Each person applies the audit's fixes in the real workspace and switches the pilot group on under the day-one rules, so day two starts with a week of real usage.
How it's earned
The credential is earned on the work, not on attendance alone. An assessor scores the learner's own artifacts against six criteria.
Proficient or better on all six rubric criteria, 80% or more on the 20-question quiz, and all 8 hours attended.
Criterion 1
Identity and access
Proficient means
Sign-in, multi-factor, provisioning and offboarding are configured and recorded.
Criterion 2
Data settings
Proficient means
Retention, training opt-outs, sharing and logging are set to match the AI policy and recorded.
Criterion 3
Connected knowledge
Proficient means
The oversharing audit was done and fixed first, and connectors use the least access each use needs.
Criterion 4
App and agent rules
Proficient means
Rules for assistants, agents, skills, plugins and connectors are set in the console and written down.
Criterion 5
Pilot and support
Proficient means
A pilot ran, usage was collected, and the runbook and incident drill are done.
Criterion 6
Operation
Proficient means
The monthly checklist is completed once, and the pilot report says what changes before rollout.
- Not yet
- Developing
- Proficient
- Exemplary
Every criterion has to reach Proficient.
A missed session is made up from the recording plus a 30-minute build check before the class meets again. If someone hasn't met the bar by the last session, I book extra one-on-one time with them at no charge until they do. Each certificate carries a verification code anyone can check at paglow.com/training/verify.
Your business owns the accounts.
They're opened by your business, billed by the software companies, and never part of the training invoice. Owning them is what keeps the work running after class.
Your company's AI, on a business plan
Admin access to the business plan the company uses or is piloting: Microsoft 365 Copilot, ChatGPT Business or Enterprise, Gemini in Google Workspace, or Claude Team or Enterprise. A trial or pilot workspace works for class if no seats are bought yet.
Microsoft 365 Copilot Business is $21 a user a month on top of a Microsoft 365 Business plan. ChatGPT Business is $25 a user a month, or $20 billed yearly. Gemini comes with Google Workspace Business Standard, about $14 a user a month billed yearly. Claude Team is $25 a seat a month, or $20 billed yearly. Billed by each provider.
Software isn't reimbursable under TechCred, so the seats are yours directly and never on the training invoice. Business plans are required because on them the provider doesn't use your business data to train its models by default.
Paglow isn't affiliated with Microsoft, OpenAI, Google or Anthropic. Microsoft 365 Copilot, ChatGPT, Gemini, Google Workspace and Claude are their makers' products.
What never goes into an AI tool
The administrator sets the controls that keep red data out of the company's AI: retention, training opt-outs, sharing and logging. These are the red lines those settings protect, by industry.
No patient information goes into any AI tool in class, ever.
Manufacturing
Red
- Export-controlled drawings or data (ITAR, EAR)
- Employee personal and medical records
- Customer data a contract keeps confidential
Healthcare administration
Red
- Anything that identifies a patient or their care (all PHI), including a name tied to a visit request
- Insurance member IDs and claims
- Staff licenses and personnel files
Trades and home services
Red
- Payment card numbers
- Gate codes and alarm codes
- Employee personal records
Professional offices
Red
- Social Security, bank and account numbers
- Privileged or confidential client material, unless office policy and a business-plan account allow it
- Tax returns and financial statements outside an approved account
What gets configured, by platform
The course runs in your own admin console. These are the settings each platform puts in front of you.
4 platform editions. Every edition earns the same AI Workspace Administrator Certificate, to the same rubric. Only the admin console changes.
Microsoft 365 Copilot
Microsoft 365 admin center
- Who gets a Copilot license, and how new staff get one
- Which SharePoint and OneDrive content Copilot can reach, after an oversharing check
- Whether people may build and share Copilot agents
- The audit and retention settings your Microsoft 365 plan includes
Microsoft 365 Copilot Business, added to a Microsoft 365 Business plan: $21 a user a month on top of the Microsoft 365 Business plan (organizations of up to 300 users). Checked 2026-10-12.
ChatGPT Business or Enterprise
ChatGPT workspace settings
- Members, roles and sign-in, including single sign-on where the plan offers it
- Which plugins, apps and connectors members may build, share or use
- The data retention and export settings the plan offers
ChatGPT Business, or Enterprise for larger companies: Business is $25 a user a month, or $20 billed yearly; Enterprise is quoted by OpenAI. Checked 2026-10-12.
Gemini in Google Workspace
Google Admin console
- Which users and teams get Gemini, by organizational unit
- Whether Gemini can draw on Gmail, Drive and other Workspace apps
- Who can create and share skills
- Drive sharing settings, checked before Gemini can search the files
Google Workspace Business Standard or higher: Included in Workspace Business Standard, about $14 a user a month billed yearly. Checked 2026-10-12.
Claude Team or Enterprise
Claude organization settings
- Members, roles and sign-in, including single sign-on where the plan offers it
- Which connectors (Google Drive, Microsoft 365 and others) members may use
- Project and sharing settings
- The data retention controls the plan offers
Claude Team, or Enterprise for larger companies: Team is $25 a seat a month, or $20 billed yearly; Enterprise is quoted by Anthropic. Checked 2026-10-12.
Plan training with this credential
Classes start in 2027. Tell me about your team and I'll reply myself with dates, a plan and the TechCred steps.
Where it leads
Pairs with the AI Policy & Governance workshop: the policy says what the settings should be.