Access for people and tools.
Identify who owns each project and who manages connections used by processes and AI. Available operations depend on the tool and its permissions. Select the specific tools and access AI needs to handle the task.
Sembot / ProductSECURITY AND ACCESSClear boundaries.
Clear boundaries.
Deliberate permissions.
Choose deployment, data access and action permissions. Control starts with who can work on your accounts and what they can do.
No account needed: review data sources, context and available actions in a sample issue.
Example workspace
Team / clients
Private access / VPN
Your infrastructureSembot
Data and configurationProcesses and tasksTools and permissions
External connections as configured
Channel APIsAI providersEmail / Twilio
Choose which external services to connect.
EXAMPLE WORKFLOW
From data scope to accountable work.
Start the access discussion with one process. Describe the data it needs, who will work with it and which activities involve an external service. This makes both deployment models easier to assess.
Map the route your data takes.
Choose one scenario and identify its source accounts, Sembot project and the people using the result. If the task involves AI or notifications, include those providers in the data-flow description.
Step outcomeA list of sources, users and services.Define the permissions needed.
Separate permission to read results from operations that change data. Check the specific integration and intended action. For Professional, include network requirements, the environment operator and how access keys will be shared and maintained.
Step outcomeAgreed access scope and responsibilities.Test before extending access.
Follow a process result through to its task and an available action in the chosen project. Check that the right people can see the context and handle missing access. For your own environment, also agree updates and data recovery.
Step outcomeA tested workflow and operational decisions.
PERMISSIONS
Connect only the scope you need.
Source data, tools and actions have their own access requirements. During configuration, decide which accounts, projects and operations your team and AI need.
- Access to data sources
- Tool and action permissions
- User responsibilities
DEPLOYMENT MODEL
SaaS or an isolated environment.
Marketer AI provides the platform as SaaS. Professional lets you run Sembot on infrastructure meeting its requirements and restrict access through a VPN.
- A model suited to your organisation
- Network access controls
- Agreed external dependencies
OPERATIONS
Plan the full working lifecycle.
Professional deployment, updates, backups and maintenance need an agreed scope. Details of data processing are covered by the legal documents and arrangements for your chosen model.
- Updates and ownership
- Backups and recovery
- Data, accounts and AI services
CHOOSE HOW TO WORK
Control extends beyond signing in.
Environment boundaries and data boundaries.
Professional supports private application access through a VPN. Plan connections to advertising APIs, AI models and notification channels separately. Your architecture review should include the destinations of requests and data.
Operations belong in the deployment scope.
Agree responsibilities for updates, backups, recovery and access changes before launch. These arrangements should fit your deployment model and organisational requirements. Record these decisions as part of the deployment scope.
BEFORE YOU START
Good to know.
Does isolated infrastructure exclude external providers?
No. Your own environment can still use external integrations and AI models. Include their scope, terms and required connections when assessing data flows. A VPN controls how users access the application.
Can my IT team review deployment details?
Share your access, infrastructure and operational requirements together with the intended scenario. We will establish the details needed for assessment. Base the assessment on deployment agreements and data-processing documents.
Can every action be automatically undone?
Action scope and error-handling options depend on the specific feature and integration. Before using an operation, check the available correction options and how to verify its outcome.
Describe one flow: source data, user, result and intended action.
List network requirements and questions from your IT team.
Identify your preferred deployment model and operational responsibilities.
Let’s scope it for your organisation.
Tell us about your team, clients and requirements. We will agree on the model, add-ons and deployment responsibilities.