Atlan Access & Platform Architect

Purpose

Key responsibilities

• Diagnose current issues. Review the existing personas, purposes, policies, and group setup. Find the root cause of the UAT visibility issues and fix them without disrupting current users.
• Design the target access framework. Build a role- and attribute-based access model that puts Client’s four access tiers into practice: Volunteers, Volunteer Leadership, Staff Leadership, and Power Users.
• Design for external users. Define how 2,000 external customers are separated from internal users. Cover discovery, metadata vs. data visibility, user roles, and licensing.
• Integrate with identity. Map access to SSO groups and automate provisioning and deprovisioning through SCIM, so access follows group membership instead of manual assignment.
• Collaborate with data architects and data engineers. Co-design the framework so it fits the underlying data architecture, classification, tagging, and pipelines. Explain and share the framework in technical terms they can build against.
• Align with governance processes. Make the platform configuration support the Two-Layer Access Approval / Expanded Use Review process and the Data Sharing & Access Authorization Agreement (DSAA).
• Validate through testing. Define UAT test cases that check expected vs. actual visibility for each persona before each onboarding wave.
• Document and hand off. Produce everything the internal team needs to run the model after the engagement ends.

Deliverables

Required experience

Skills

• Translates governance tiers and approval workflows into a documented, testable access matrix.
• Least-privilege design, access reviews, and audit logging.
• Familiar with privacy and contractual controls for external data sharing.
• Works well with technical peers, especially data architects and data engineers.
• Documents clearly and builds for handoff.

Requirements

• Translates governance tiers and approval workflows into a documented, testable access matrix.
• Least-privilege design, access reviews, and audit logging.
• Familiar with privacy and contractual controls for external data sharing.
• Works well with technical peers, especially data architects and data engineers.
• Documents clearly and builds for handoff.