Connect tools with clear permissions
Choose the right account, grant access only to the employees who need it, and review what external actions may happen.
Connect for a specific job
Before connecting an app or account, name the job it should support. A support employee may need to find an order; a marketing employee may need to read campaign results. Avoid connecting an account simply because it is available.
Setu’s Connections area supports configured app sign-ins and account details. The choices depend on your workspace setup and the service. Complete the provider’s sign-in or setup, then verify the connection before use.
Grant access to selected employees
After setup, choose which employees may use the connection. A connected account is not automatically available to every employee. Revisit the grants when an employee changes role or no longer needs that access.
Use the narrowest account access the provider offers. Setu can enforce which employee has a grant, but it cannot make an overly broad permission inside the provider’s account narrower.
Decide which actions need approval
Setu separates access to a tool from permission to take an action. In Settings → Approvals, owners can choose whether actions such as sending, publishing, deleting or changing account data always need approval, may proceed without asking, or are never allowed. Sending, paying, publishing and deleting begin with approval required; a trusted tool does not bypass that rule.
Review the rule for the company, department and employee. A narrower rule can override a broader one. Check the available options and their effect before changing them.
Check and revoke access
Use connection status and the employee’s tool list to confirm the setup is ready. If an account is no longer needed, revoke its grant or disconnect it. Then review pending work that may have been waiting for that connection.
Explore Setu
Read the product guide or explore a demo workspace.