Company overview

In this detailed overview, you can see a lot of statistics about your company, its organizations, and their application.

After reading this article you'll know:

• What the company overview is

• Which statistics you can find in the overview

• Which classifications of users and applications there are

An expansion for application management within My Betty Blocks — the company overview. This feature offers users insight into their application landscape, allowing you to gain a better understanding of your user and application data.

Company admins

To get there, we have added the company admin role. Positioned one level above the current organization layer, this new role with a new permission is created to enable your organization admin, now elevated to a company admin, to view all data available in the company overview.

Let's have a look at what exactly, the company overview has to offer.

Total applications

Gain a panoramic view of all your applications in one centralized location. Whether you're managing a handful or a multitude of applications, the company overview enables you to keep track of each one effortlessly.

At Betty Blocks we recognize multiple types of applications, to read more about the different kinds of applications check out this article.

Total builders and internal users

See the usability dynamics of your application with a breakdown of total builders and internal users. Internal Users are required to log in using credentials to access the applications, identified by an email domain associated with the company. This insight allows you to better understand your team's composition and application resource usage. The total amount of internal and external users is updated monthly. The other statistics on the company overview are updated at 00:00 CET.

Builders are users who have registered in Betty Blocks and have a building role within an application.

Included in the count:

Builders that are inactive

Excluded from the count:

Builders with a Betty Blocks domain name.

Builders that are part of one of our implementation partners assigned to the customer.

Best practices:

The admin should review the users monthly to remove inactive builders and check for duplicates.

• The admin should review the users monthly to remove inactive builders and check for duplicates.
• Authenticated users are users required to log in to access specific applications, with an email domain belonging to the customer's company.

Included in the count:

• Every item in a data model that is connected to an authentication profile (ability to log in to the application with that model) including my Betty Blocks/builder logins in the IDE

• The same person with 2 email addresses counts as 2 users, based on their email addresses. For example, JohnD@examplecompany.com and JohnDoe@examplecompany.com are counted as 2 users, even if they refer to the same person.

• Internal users with zero or no activity.

• Internal users that log in with a user name.

• Users who no longer work in the company but are not removed.

• Single Sign-On (SSO): If SSO is implemented we look for internal users that have an email belonging to a customer's company, if not it is an external user.

• If we are unable to find the email address, all records in that model are counted as unique external users, this may result in a higher external user count

Excluded from the count:

• Internal users with a Betty Blocks domain name.

• Internal users that are part of one of our implementation partners assigned to the customer.

Best practices:

• The admin should review the users monthly to remove inactive users and check for duplicates.

• The admin should provide Betty Blocks (BB) with a list of domain names that qualify as internal.

Included in the count:

• The same person with 2 email addresses counts as 2 users, based on their email addresses. For example, JohnD@customercompany.com and JohnDoe@customercompany.com are counted as 2 users, even if they refer to the same person.

• Internal users who log in with a different domain name than the specified domain list.

• Users who log in only once.

• External users that log in with a user name.

• User records that have no way of being connected to the registered email domain of the company.

• Inactive external users.

• If we are unable to find the user information, all records in that model are counted as unique external users, this may result in a higher external user count

Excluded from the count:

• Users with a Betty Blocks domain name.

Best practices:

• The admin should review the users monthly to remove inactive users and check for duplicates.

• The admin should inform Betty Blocks (BB) if they plan to undertake an activity that would temporarily increase the number of external users, requiring a separate agreement.

Included:

• Everybody that is not authenticated.

Excluded:

• Anonymous is the role they have in the application. A person who logs in, but is not traceable to privacy is not called anonymous.

Total templates

The creation of your ultimate application factory can only be done with a sub-set of wonderfully crafted application templates. All templates shared within the organization will display in a panoramic overview, allowing you to have a glance at what can be created in a matter of minutes.

Total building blocks

Understand the parts of your production applications by exploring the total number of building blocks. These building blocks exist of pages, data models, actions, and web services, each defined within your Betty Blocks contract. The company overview offers a different view of your application, allowing you to view the complexity and scale, and in turn, allowing you to measure effectiveness and resources.

Included in building blocks:

• Multiplier per building block content type as described in a contract

• All building blocks that are in the default production applications

  • Pages (current-gen)

  • Actions (current-gen & classic)

  • Models (current-gen & classic)

  • Custom models (current-gen)

  • Webservices (classic)

  • Custom endpoint (classic)

• Building blocks in disabled applications

• Building blocks that aren’t used anymore

• Building blocks that need to be built for a workaround

Excluded:

• Building blocks in sandboxes of default applications

• Building blocks in playground applications

• Building blocks in training applications

1. Building blocks in sandboxes of default applications
2. Building blocks in playground applications
3. Building blocks in training applications
   
   Best practices:

• The admin should review the apps and functionality on usage, and decide to remove items.

• Playground and training apps need to be removed after 3 months

Moving your application

Applications reside within the organization in which they have been created. Sometimes, however, it might be that you want to move the application to another organization if a copy based on an application template does not suffice.
You can move your application in the settings of the application, however as a company admin you can also move applications in the application overview of your company. Navigate to the global overview and press the arrow button on an applications record. A prompt will appear in which you can select the new organization you want to move your application to.

 

Note: It is important to look into your roles and permissions, as you need corresponding ones to move applications from one to another organization.