A platform admin in Betty Blocks is responsible for managing roles, permissions, and overall governance within the platform. Unlike developers or builders, the platform admin does not engage with the application-building processes. Instead, they focus on maintaining control over the platform’s operational aspects, ensuring compliance, efficiency, and proper access management across the organization.
Responsibilities of a platform admin
Meet Jennifer Poleti, a functional manager with a strong background in business IT management. In her role at Betty Blocks, she oversees application usage and costs, diligently monitoring roles and permissions to make sure that all team members have the appropriate level of access based on their responsibilities.
The platform admin is essential in maintaining a secure and organized environment within Betty Blocks. Key responsibilities include:
Monitoring application usage and compliance: The admin closely tracks how different applications are used within the organization, adhering to company policies and industry regulations.
Managing roles and permissions: A major part of the admin’s role is assigning roles and permissions to users. Jennifer ensures that each person has the correct access level, providing the necessary permissions for their job while covering up sensitive areas.
Overseeing application costs: Platform admins keep a detailed overview of all applications in use, analyzing how much each application is used compared to the associated costs. This understanding helps make informed decisions about scaling or adjusting application use to optimize organizational efficiency and manage costs.
Practically, all of these goals connected with role and permissions management and other governance tools are handled via My Betty Blocks section of our platform.
Connection with other roles
Jessie Kiran (citizen developer): Jennifer ensures Jessie receives a citizen developer role, granting her limited access that matches her responsibilities. This helps Jessie avoid an overwhelming interface and minimizes the risk of inadvertently disrupting the application.
James Linh (business technologist): James, with his business technologist role, typically has extensive access to the platform. Jennifer manages occasional restrictions, especially concerning data model permissions, aligning James’s access with project needs.
Samuel Oak (low-code developer): Samuel’s role requires full development access. Jennifer ensures he has complete control, allowing him to secure and customize the application as needed, making sure he can operate without constraints.
Overall, the platform admin role is essential in Betty Blocks for maintaining governance, compliance, and security within the platform. Our example demonstrates how an admin bridges the gap between operational management and technical roles, providing the right access and oversight.