Sisense Community logo
    • Community Feedback
    • Chapters
    • Events
    • Forums
      • Help and How To
      • Product Feedback Forum
      • Strategy & Use Cases
    • Blogs
    • KB Docs
      • KB Docs
      • Add-Ons & Plug-Ins
      • APIs
      • Best Practices
      • Blox
      • CDT
      • Cloud Managed Service
      • Data Models
      • Data Sources
      • Embedding Analytics
      • How-Tos & FAQs
      • Onboarding
      • PySisense
      • Security
      • Sisense Administration
      • Sisense Intelligence & AI
      • Troubleshooting
      • Widget & Dashboard Scripts
    • Support
    • Learning
      • Sisense Academy: Free Courses and Certifications
      • Official Developer Documentation
      • Official Product Documentation
      • Official Sisense Youtube Channel
      • Sisense Compose SDK Playground
      • Official Sisense Discord
    • Use Case Gallery
    Discussions
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   
    Discussions
    • TagsChevronRightIcon
    GIT
      • Sisense AdministrationChevronRightIcon

      GIT Instruction How To

                                               

      GIT Instruction How To In order to migrate Sisense assets between environments, please follow the below steps: Step to add your assets to the GIT repository:   1. Create a project by adding a project name along with a default branch name (such as master, POC, or any meaningful name)   2. Add your GIT repository which could be remote or local.  Below screenshot shows remote repository:      3. When you execute the test to GIT, the system will show connection was successful.       4.  You can either choose the option to create and continue or create and close buttons     5.  You can either share your project with others or continue to the next step:     6. At this point, you have two options to add Assets.  You can add one in below screen and add it to your project:    7.  Or you can save the project close, and add asset by clicking “managing asset”     8. After adding your assets, we should choose the project:   9. Then select all uncommitted changes;  add a comment for your added assets and commit the new changes.     10.  Now you push the assets so the newly added objects will be sent to the repository. 11. The Sisense application will need your GIT application credentials to proceed: Steps to add assets from GIT to another instance: 1. You will need to create a project in the second instance:   Click create project and continue 2. At this step, you can share the new project with other team members if needed: Save and close the project.   3. Then choose pull from your GIT repository and make sure you add the correct branch as seen in below screenshot:   4. The system again will ask for credentials: Where the pull action, will ask for credentials:       5. And it will update the project: 6.  You will then need to pull your added Assets and add your note; and commit afterward: You should then see your assets in the prod instance.  In our ex ample, map elasticube was added. For more information, you can check out the following Articles: https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-git-integration.htm https://www.sisense.com/platform/git-integration/ https://community.sisense.com/t5/knowledge/elevate-your-data-product-s-quality-with-streamlined-version/ta-p/15131

      Vicki786
      Vicki786Posted 1 year ago • Last reply 1 year ago
      3
               
      • Add-ons & Plug-InsChevronRightIcon

      How to Hide the Git Button for Certain User Groups in Sisense (Linux)

                                               

      How to Hide the Git Button for Certain User Groups in Sisense (Linux) This article guides how to restrict access to the Git button for a specific user group in Sisense. This ensures that certain users do not gain access to Git projects they should not see.   [ ALT Text: A dashboard interface titled "Analytics" with a welcome message. It features icons for "Videos," "Tutorials," and "Documentation" on the left, and a sample healthcare dashboard with insights on patient admissions and costs on the right. There is a navigation menu at the top right with user and notification icons.] Step-by-Step Guide Download a sample plugin attached. Upload the add-on to the /plugins directory on your Sisense environment using File Manager: https://docs.sisense.com/main/SisenseLinux/uploading-files-to-customize-your-linux-deployment.htm Create a "Test"  group and add a user to it that should not have access to the Git button. The plugin checks for a user group named "Test".  After installation and configuration, test by logging in as a user from the restricted group and verify the Git button is hidden. Note: The current version of the plugin requires the group's name to remain as "Test"; customization for other group names requires further development within the run.js file. Limitations The hidden Git button might have a delay before disappearing as the plugin fetches user data post-initialization. Direct role-based modifications are not available; only group-based restrictions are possible with the provided plugin. Conclusion By using the provided plugin, you can effectively restrict access to the Git button for certain user groups in Sisense.  Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this please let us know.

      Liliia Kislitsyna
      Liliia KislitsynaPosted 1 year ago
      0