The Manage Projects Page allows you to view all of your projects in one place, along with their respective models. Each model can be restricted to specific database connections if so desired. By doing so, Admins are able to limit developers to certain databases by limiting those users’ models.
This page can be quite confusing if you do not have the proper mental picture of how it works. The key thing to remember is that you can create project and model configurations here, even if those projects and models don’t yet exist in your LookML.
For everything to work properly, you need to make sure that your LookML and this page match each other. By “match” we mean that the model files you create in the LookML section of Looker have a corresponding configuration on this page, and vice versa.
This section of the page displays all of your existing projects. The Configured Projects (Ready to add LookML) (described in more detail below) is a bit of a misnomer, and actually contains model configurations that don’t have an existing project yet.
Note that each user may see a different list of projects and models on this page, based on their permissions. You may also see a difference between development mode and production mode on this page. For example, if you might have created a new model in development mode that you have not yet pushed to production.
This is the name of the project. Each project may have one or more models listed next to it.
The set of LookML model files for the given project. Please note that if your development mode environment differs from production, this list can change between development mode and production mode. For example, if you might have created a new model in development mode that you have not yet pushed to production.
|OK||This is the desired state|
|Missing LookML Model||It is possible to configure a model on this page, even if you haven’t already created a corresponding LookML file for it. In this scenario, you will see this issue.|
|Not Configured||If you create a new LookML model file in an existing project, but have not yet configured it on this page yet, you will see this issue|
|Connection ‘x’ does not exist||The
|Model ‘x’ is not allowed to use connection ‘y’||The
|A model named ‘x’ is already configured in project ‘y’||Model names must be unique within your Looker instance, even if they are in different projects|
Use this link to edit or delete your model configuration. Here you can change which connections are available to the model.
You will not be able to re-name a model here. Models are named according to the filenames you use in the Models section of the Looker IDE (more details here).
Deleting a project will remove it from all dev and production environments across your Looker instance.
Please be certain you want to delete a project before you do so. It cannot be undone and is difficult and laborious to recover.
Configured Projects (Ready to add LookML)
The name of this section is a bit of a misnomer. It contains model configurations that do not yet have an associated project. Items can enter this state if you use the Configure a Model button without providing an existing project name when you create it.
This is the name of the project that was provided when the model configuration was created.
This is the name that was provided when the model configuration was created.
These are the connections that were allowed for this model when the model configuration was created.
This link allows you to change the connections that are permitted for this model.
[+ New LookML Project] Button
Use this button to create a new project using the LookML generator. Looker asks for the connection on this page so that it can automatically generate LookML based on a set of tables in your database. However, you can still add additional connections later.
[+ Configure a Model] Button
Use this button to pro-actively configure a model before it is added to the LookML. You can add the model to an existing project, or provide a project name that doesn’t exist yet as a placeholder.
In production mode, any model that is not configured on this page will not return results. Model configuration is required in production mode.
A model configuration is not needed for Admins (or developers with the
manage_modelspermission) while they are in development mode. However, if a model configuration does exist, any queries will be constrained by that configuration. This allows developers to work easily while in development mode, while still requiring a purposeful decision for production users.
When admins (or developers with the
manage_modelspermission) push a project to production, Looker will attempt to automatically configure any models in the project that were not previously configured.