Security and Access Control in a Shared Fusion Team
A Fusion organization has multiple teams: Marketing, Sales, and IT. The Marketing team has built several scenarios that access sensitive customer data from the CRM and send it to a marketing platform. The Sales team also needs to use some of these scenarios but should not see the credentials or modify the scenario logic. The IT team manages the connections and wants to ensure that only authorized users can execute scenarios that handle PII. Currently, all users are in the same team with full access, leading to accidental modifications and credential exposure. The organization wants to implement least privilege access.
1. How would you structure teams and permissions to meet these requirements?
Read the worked answer
Create separate teams for Marketing, Sales, and IT. In Fusion, teams control access to scenarios, connections, and other resources. Assign users to appropriate teams based on their role. For the Marketing team, give them 'Team Admin' or 'User' roles as needed to build and manage their scenarios. For Sales, add them to a team that has 'User' access but only to specific scenarios? Actually, Fusion's sharing model: scenarios can be shared with other teams with 'Run only' or 'View' permissions. So, keep the scenarios in the Marketing team, and share them with the Sales team with 'Run only' permission. This allows Sales to execute but not edit or see credentials. Connections are owned by the team; to prevent Sales from seeing credentials, ensure connections are created in the Marketing or IT team and not shared. For IT, they can have a team with 'Admin' rights to manage connections and monitor. Use role-based access: 'Owner', 'Admin', 'Member', 'Operator', 'Viewer'. Set the Sales users as 'Operator' or 'Viewer' on shared scenarios. Also, use 'Connections' with restricted scopes and store them in a team that Sales cannot access. Enable 'Audit log' to track changes.
2. What measures would you take to protect sensitive data and credentials?
Read the worked answer
Use Fusion's connection management: create connections with the minimum required scopes (e.g., read-only if possible). Store connections in a team that only IT and Marketing admins can access. Do not share connections with other teams; instead, share scenarios that use those connections with 'Run only' permission, so the executing user does not need to see the connection details. Enable 'Credential encryption' if available. Also, use 'Data privacy' features: mask sensitive data in logs by using 'Secure' fields or disabling logging of certain modules. Restrict scenario execution to specific IP ranges if needed. Implement 'Two-factor authentication' for all users. Regularly review access and use 'Audit logs' to monitor connection usage. For PII, consider using 'Data store' with encryption or avoid storing PII in Fusion. Ensure that error messages do not expose sensitive data by customizing error handlers.