Account instructions
Broad preferences and rules that apply across conversations.
Give Claude the right business knowledge, working rules and permissions, then train your team to use it on real work with clear human oversight.
I help Australian founders and teams move from individual experiments to a practical Claude setup that people can understand, use and maintain.
The quick answer
A proper Claude setup includes the right account or organisation, clear instructions, structured business knowledge, task-specific Projects, repeatable Skills, carefully selected connectors, permission and approval rules, staff training, and a way to test whether the work is reliable.
The aim is not to give everyone a chatbot and hope they use it well. It is to create a shared way of working that reflects how the business already makes decisions.
The setup stack
Anthropic distinguishes background knowledge, procedures and external access. Treating them as different layers makes Claude easier to govern and maintain.
Broad preferences and rules that apply across conversations.
Focused workspaces with their own knowledge and instructions.
Reusable procedures for specialist or repeatable tasks.
Permissioned access to external apps, data and supported actions.
Delegated multi-step work inside a defined environment.
Choose the workspace
Useful for personal instructions, Projects and Skills and for piloting low-risk internal work. Review the terms and data settings that apply to the account.
Intended for organisations with at least two members. It creates a separate organisation where shared Projects, roles and organisation-managed capabilities can support consistent work.
For organisations that need stronger identity, access, administration and monitoring controls. Suitability depends on security, privacy, procurement and compliance requirements.
Do not choose a plan only by feature count. Decide who will use Claude, what information they need, whether knowledge should be shared, which actions are permitted and who owns the workspace.
The implementation method
Start with a defined result such as a management brief, client onboarding pack, content workflow or enquiry triage process.
Assign one person to own the use case, source information, access, testing and review date.
Decide whether the work belongs in an individual account, Team organisation or Enterprise environment.
Document approved tools, prohibited information, minimum permissions and actions Claude must not take.
Add current, governed knowledge rather than a random document dump.
Organise related knowledge and instructions around a real function or workflow.
Use Skills for procedures and connectors only when approved external access is required.
Practise with representative work, compare outputs with evidence and review whenever the system changes.
The business context
Deb created the AI Brain for Business from 30 years of working with businesses on marketing, strategy and growth. It brings Business DNA and Brand DNA together to capture the intelligence AI needs.
The Business DNA covers strategy, audience, offers, customer knowledge, goals and the Revenue Roadmap. The Brand DNA covers positioning, messaging, voice and communication rules. Together, they give Claude more relevant context and reduce repeated briefing.
The AI Workspace then makes that intelligence usable by connecting it to filing rules, Projects, Skills, workflows, tools and human approval points.
Explore the AI Brain for BusinessConnectors and permissions
Connectors allow Claude to retrieve information and, where supported and enabled, take actions in connected services. Anthropic says connectors inherit each person's permissions from the source service.
That does not remove the business's responsibility to review read and write capabilities, the information involved and the approval experience. Start with read-only or low-risk actions where possible. Test with a draft, copy or reversible task before allowing a live action.
Claude for Work accounts on Team or Enterprise plans are governed by the agreement between Anthropic and the organisation. Anthropic's published guidance distinguishes these commercial products from individual Free, Pro and Max accounts.
An Australian business should still conduct its own due diligence and apply its privacy, security, contractual, intellectual property and sector requirements.
This page provides practical implementation guidance, not legal, privacy, cyber security or regulatory advice.
Team capability
A useful team session is not a tour of clever prompts. People need to understand the approved use case, source information, data rules, account and Project structure, repeatable Skill or workflow, evidence checking and human approval points.
The strongest training uses the team's own low-risk work. Participants practise one approved task, compare results, find the failure points and leave with a shared operating method.
Prepare for setup
One clear workflow, the current source documents and examples of good and poor results.
The people who own, complete and approve the task, including the decision that remains human.
Known privacy, security, legal and contractual limits plus the tools and data sources involved.
Work with Deb
A focused 1:1 session to choose the use case, map the bottleneck and decide the right Claude setup before a larger build.
$497
Book your Power HourTwo private days to build the business intelligence foundation, Revenue Roadmap, governed AI Workspace and tailored operating systems.
$6,997 AUD plus GST
Explore the immersionPractical sessions covering Claude setup, business context, workflows, human oversight and responsible use connected to real work.
Enquire about trainingAbout the author
Deb Szabo brings 30 years in marketing to her work as an AI Business Strategist and Claude Specialist. She passed the official proctored Claude Certified Associate - Foundations exam set by Anthropic, has completed eight separate Anthropic course credentials and is registered in the Claude Partner Network. Claude Certified Architect - Foundations is in progress.
Based in Pokolbin in the Hunter Valley, NSW, Deb helps Australian businesses turn existing knowledge into governed AI systems and useful day-to-day capability.
View Claude credentialsClear answers
Choose one business outcome, name the owner, select the right account or organisation, set data and approval rules, add governed business knowledge, build one focused Project or workflow, then train and test with real examples. Expand access only after the first workflow is reliable.
The right plan depends on the number of users, whether Projects and knowledge need to be shared, the required administrative controls, applicable commercial terms and the sensitivity of the work. A solo operator may begin with an individual plan. Claude Team is intended for organisations with at least two people. Larger or higher-control organisations should assess Enterprise requirements with their security, privacy and procurement stakeholders.
Claude Team is designed for organisations with at least two members and provides a separate organisational workspace. Whether it is the right choice depends on the need for shared Projects, organisation-managed capabilities, roles, permissions and commercial account governance.
Projects hold focused background knowledge and project instructions. Skills teach Claude a repeatable method for a task. Connectors give Claude permissioned access to external services and data. They can work together, but each solves a different part of the setup.
Anthropic provides Google Workspace connectors for Gmail, Google Calendar and Google Drive. The current guidance says Claude mirrors the connected user's permissions and only accesses data when requested. Available read and write actions, approval requirements and limitations should be checked in the current connector documentation before use.
The answer depends on the product and governing terms. Anthropic states that customer content from Claude for Work and the API is not used to train its models by default under commercial terms. Anthropic separately documents data choices for individual consumer accounts. Confirm which account and terms apply before adding business information.
Some connectors can take supported actions when the required permissions and tools are enabled. The capability varies by connector and configuration. Review the connector's current read and write permissions, keep access limited, test low-risk actions first and retain human approval for customer-facing, high-impact or irreversible work.
Training should cover the approved use case, source information, data rules, account and Project structure, the repeatable workflow or Skill, evidence checking, human approval points, failure reporting and ongoing review. The team should practise on representative work rather than only watching demonstrations.
Deb Szabo provides Claude setup, practical AI implementation and team training for Australian businesses. She works from Pokolbin in the Hunter Valley with in-person and virtual delivery across Australia.
The scope depends on the number of people, workflows, systems, data risks and tailored installation required. Deb's 1:1 AI Business Power Hour is $497. Her private Tailored AI Brain for Business VIP Immersion is $6,997 AUD plus GST. Team training and workshop scopes are quoted according to the audience, format and required implementation work.
Written by Deb Szabo, AI Business Strategist and Claude Specialist. Last reviewed 7 August 2026. For the wider implementation method, read How to Implement AI in an Australian Small Business.
Your practical next step
Bring the use case. Leave with the right account, context and implementation path.