Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Add-on Google Workspace yang menambahkan solusi konferensi sering kali memiliki detail yang harus dikontrol oleh pengguna dari halaman setelan add-on. Misalnya, tombol atau kontrol yang memungkinkan pengguna logout dari sistem konferensi pihak ketiga adalah hal yang umum.
Halaman setelan add-on bersifat opsional. Bagian berikut menjelaskan cara membuka halaman setelan add-on dan cara membuat halaman setelan.
Membuka setelan add-on
Anda dapat membuka halaman setelan add-on yang telah diinstal dengan melakukan
tindakan berikut:
Di panel navigasi kiri, pilih add-on untuk membuka daftar add-on yang diinstal.
Klik tombol Setelan yang muncul di sebelah kanan nama add-on
untuk membuka halaman setelan add-on tersebut; tindakan ini akan menyebabkan Google Kalender
membuka URL halaman setelan.
Jika add-on tidak menentukan halaman setelan, tombol Setelan tidak
muncul.
Membangun halaman setelan
Halaman setelan umumnya dibuat menggunakan HTML dan CSS standar. Saat mendesain
halaman, ikuti
panduan gaya add-on.
Saat pengguna menyesuaikan setelan add-on, halaman harus mengirim
permintaan ke sistem konferensi pihak ketiga untuk menerapkan perubahan tersebut sebagaimana
mestinya. Halaman juga dapat menyimpan dan mengambil informasi dari project add-on properti pengguna sesuai kebutuhan.
Dihosting di server web eksternal
Anda dapat menghosting halaman setelan add-on secara eksternal dari project skrip add-on, mungkin sebagai bagian dari situs konferensi pihak ketiga.
Untuk menautkan add-on ke halaman setelan eksternal, Anda harus melakukan hal berikut:
Buat halaman dan host secara eksternal. Saat menambahkan elemen ke halaman,
pastikan elemen tersebut berkomunikasi dengan benar dengan sistem konferensi pihak ketiga
dan lakukan perubahan yang sesuai untuk pengguna tersebut.
Di project skrip add-on, terapkan fungsi yang menampilkan URL
untuk halaman eksternal.
Tentukan nama fungsi ini sebagai kolom calendar.createSettingsFunction
dalam project add-on
manifes.
Dihosting dalam Apps Script
Anda dapat menyediakan halaman setelan untuk add-on menggunakan
aplikasi web Apps Script. Sebagai aplikasi web, project skrip add-on
dapat membuat dan men-deploy halaman, yang kemudian dihosting di server Apps Script.
Lihat panduan Layanan HTML
untuk mengetahui detail tentang cara membuat HTML untuk aplikasi web. Halaman setelan Anda dapat
berkomunikasi dengan server Google
sesuai kebutuhan. Anda juga dapat memanfaatkan
template di halaman untuk membuatnya lebih
dinamis.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-29 UTC."],[[["\u003cp\u003eGoogle Workspace add-ons for conferencing can include optional settings pages built with standard HTML and CSS, hosted externally or within Apps Script.\u003c/p\u003e\n"],["\u003cp\u003eAdd-on settings allow users to control details like logging out of the third-party system and are accessed via Google Calendar's settings.\u003c/p\u003e\n"],["\u003cp\u003eWhen building an external settings page, ensure elements interact correctly with the conferencing system and the add-on manifest links to its URL.\u003c/p\u003e\n"],["\u003cp\u003eApps Script web apps offer an alternative hosting option, enabling communication with Google servers and dynamic content through templates.\u003c/p\u003e\n"],["\u003cp\u003eWhen using Apps Script for settings pages, maintain consistent project version numbers across deployments to ensure proper functionality.\u003c/p\u003e\n"]]],["Google Workspace add-ons with conferencing features can have optional settings pages. Users access these pages through Google Calendar's add-on settings. Developers build settings pages using HTML and CSS, hosted either externally or within Apps Script. The settings page should allow users to adjust add-on behaviors, communicating with the third-party system to enact changes, storing data in user properties. To link externally, developers specify the URL in the add-on's manifest file. For Apps Script, they use web apps and must maintain consistent project versions between the add-on and settings page.\n"],null,["# Adding conferencing add-on settings\n\n| **Note:** This functionality was built for conference providers specifically, and was originally available as *[Calendar conferencing add-ons](/workspace/add-ons/guides/glossary#calendar_conferencing_add-on)*.\n\nGoogle Workspace add-ons that add conferencing\nsolutions often have details that should be controlled by the user from an\nadd-on *settings page*. For example, it is common to have a button or control\nthat lets a user log out of the third-party conference system.\n\nAdd-on setting pages are optional. The following sections describe how to open\nan add-on's setting page and how to build a setting page.\n\nOpen add-on settings\n--------------------\n\nYou can open the settings page of an add-on you have installed by doing the\nfollowing:\n\n1. Open [Google Calendar](https://calendar.google.com/).\n2. Click the settings icon and select **Settings**.\n3. In the left navigation panel, select **add-ons** to jump to the installed add-on list.\n4. Click the **Settings** button that appears to the right of the add-on name to open the settings page for that add-on; this causes Google Calendar to open the settings page URL.\n\nIf an add-on does not define a settings page, the **Settings** button does not\nappear.\n\nBuild a settings page\n---------------------\n\nA settings page is generally built using standard HTML and CSS. When designing\nyour page, follow the\n[add-on style guidelines](/workspace/add-ons/guides/workspace-style).\n\nWhen a user makes adjustments to the add-on settings, the page should send\nrequests to the third-party conferencing system to enact those changes as\nappropriate. The page can also store and retrieve information from the add-on\nproject [user properties](/apps-script/reference/properties) as needed.\n\n### Hosted on an external web server\n\nYou can host your add-on setting page externally from the add-on script project,\nperhaps as part of the third-party conferencing website.\n\nTo link an add-on to an external setting page, you must do the following:\n\n1. Build the page and host it externally. When adding elements to the page, be sure that they communicate correctly with the third-party conferencing system and make the appropriate changes for that user.\n2. In the add-on script project, implement a function that returns the URL for the external page.\n3. Specify the name of this function as the `calendar.createSettingsFunction` field in the add-on project [manifest](/workspace/add-ons/concepts/workspace-manifests#manifest_structure_for_g_suite_add-ons).\n\n### Hosted within Apps Script\n\nYou can provide a settings page for your add-on by using an Apps Script\n[web app](/apps-script/guides/web). As a web app, your add-on script project\ncan build and deploy the page, which is then hosted on the Apps Script servers.\n\nSee the [HTML Service guide](/apps-script/guides/html#serve_html_as_a_web_app)\nfor details on how to build HTML for web apps. Your settings page can\n[communicate with the Google servers](/apps-script/guides/html/communication)\nas needed. You can also make use of\n[templates](/apps-script/guides/html/templates) in the page to make it more\ndynamic.\n\nThe\n[Calendar conferencing add-on example](/workspace/add-ons/samples/conferencing-sample)\nshows how to construct a web app settings page.\n| **Caution:** When deploying a web app page for use, you must provide a script project [version](/apps-script/guides/versions). You also provide a project version when deploying the add-on. As you update your script project to new versions, always be sure that the version number for the deployments matches. Otherwise your add-on may exhibit unexpected behavior."]]
