Tetap teratur dengan koleksi Simpan dan kategorikan konten berdasarkan preferensi Anda.
Skrip terikat ke file Google Spreadsheet, Dokumen, Slide, atau Formulir jika skrip tersebut dibuat dari dokumen tersebut, bukan sebagai skrip mandiri. File yang dilampirkan ke skrip terikat disebut "penampung". Skrip terikat umumnya berperilaku seperti skrip mandiri, kecuali bahwa skrip tersebut tidak muncul di Google Drive, tidak dapat dilepas dari file yang terikat dengannya, dan mendapatkan beberapa hak istimewa khusus atas file induk.
Perhatikan bahwa skrip juga dapat terikat ke Google Sites, tetapi skrip ini hampir selalu di-deploy sebagai aplikasi web. Skrip yang terikat ke Google Spreadsheet, Dokumen, Slide, atau Formulir juga dapat menjadi aplikasi web, meskipun hal ini jarang terjadi.
Membuat skrip terikat
Google Dokumen, Spreadsheet, atau Slide
Untuk membuat skrip terikat di Google Dokumen, Spreadsheet, atau Slide, buka dokumen di Dokumen, spreadsheet di Spreadsheet, atau presentasi di Slide, lalu klik Ekstensi>Apps Script. Untuk membuka kembali skrip di masa mendatang, lakukan hal yang sama atau buka skrip dari dasbor Apps Script.
Google Formulir
Untuk membuat skrip terikat di Google Formulir, buka formulir dan klik Lainnya more_vert>Editor skrip. Untuk membuka kembali skrip di masa mendatang, lakukan hal yang sama atau buka skrip dari dasbor Apps Script.
Metode khusus
Skrip terikat dapat memanggil beberapa metode yang tidak dapat dilakukan oleh skrip mandiri:
Skrip terikat dapat menyesuaikan Google Spreadsheet, Dokumen, dan Formulir dengan menambahkan menu kustom dan kotak dialog atau sidebar. Namun, perlu diingat bahwa skrip hanya dapat berinteraksi dengan antarmuka pengguna untuk instance file terbuka saat ini. Artinya, skrip yang terikat ke satu dokumen tidak dapat memengaruhi antarmuka pengguna dokumen lain.
Pemicu
Skrip terikat dapat menggunakan pemicu sederhana seperti fungsi onOpen() khusus, yang berjalan secara otomatis setiap kali file dibuka oleh pengguna yang memiliki akses edit. Seperti semua jenis skrip, skrip ini juga dapat menggunakan pemicu yang dapat diinstal.
Fungsi kustom
Fungsi kustom adalah fungsi dalam skrip yang terikat ke Google Spreadsheet yang Anda panggil langsung dari sel menggunakan sintaksis =myFunctionName(). Dengan demikian, fungsi kustom mirip dengan ratusan fungsi bawaan di Spreadsheet seperti AVERAGE atau SUM, kecuali Anda menentukan perilaku fungsi kustom.
Akses ke skrip terikat
Hanya pengguna yang memiliki izin untuk mengedit penampung yang dapat menjalankan skrip terikatnya. Kolaborator yang hanya memiliki akses lihat tidak dapat membuka editor skrip, meskipun jika mereka membuat salinan file penampung, mereka akan menjadi pemilik salinan dan dapat melihat serta menjalankan salinan skrip.
[[["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-04 UTC."],[[["\u003cp\u003eBound scripts are Google Apps Scripts attached to Google Docs, Sheets, Slides, or Forms, offering special privileges to interact with their parent file.\u003c/p\u003e\n"],["\u003cp\u003eUnlike standalone scripts, bound scripts reside within their container file and cannot be detached, functioning like unpublished add-ons specific to that file.\u003c/p\u003e\n"],["\u003cp\u003eThey allow the use of special methods to programmatically access and manipulate the parent file's content and user interface.\u003c/p\u003e\n"],["\u003cp\u003eBound scripts can be shared by sharing the container file, enabling collaborators with edit access to run the script.\u003c/p\u003e\n"],["\u003cp\u003eThese scripts can also be published as add-ons, making them accessible to a wider audience through the add-on store.\u003c/p\u003e\n"]]],[],null,["A script is bound to a Google Sheets, Docs, Slides, or Forms file if it was\ncreated from that document rather than as a [standalone script](/apps-script/guides/standalone).\nThe file that a bound script is attached to is called a \"container.\"\nBound scripts generally behave like standalone scripts except that they\ndo not appear in Google Drive, they cannot be detached from the file\nthey are bound to, and they gain a few special privileges over the parent file.\n\nNote that scripts can also be bound to Google Sites, but these scripts are\nalmost always deployed as [web apps](/apps-script/guides/web). Scripts\nbound to Google Sheets, Docs, Slides, or Forms can also become web apps, although\nthis is uncommon.\n| **Note:** Bound scripts are effectively unpublished [add-ons](/workspace/add-ons/concepts/types#editor_add-ons) that function only for the file they are bound to.\n\nCreate a bound script\n\nGoogle Docs, Sheets, or Slides\n\nTo create a bound script in Google Docs, Sheets, or Slides, open a document in\nDocs, a spreadsheet in Sheets, or a presentation in Slides and click\n**Extensions**\n\\\u003e **Apps Script** . To reopen the script in\nthe future, do the same thing or open the script from the\n[Apps Script dashboard](https://script.google.com/home).\n\nGoogle Forms\n\nTo create a bound script in Google Forms, open a form\nand click More more_vert\n\\\u003e **Script\neditor** . To reopen the script in the\nfuture, do the same thing or open the script from the\n[Apps Script dashboard](https://script.google.com/home).\n| **Note:** The [`clasp`](/apps-script/guides/clasp) tool can't create bound scripts, but it can clone and edit them.\n\nSpecial methods\n\nBound scripts can call a few methods that standalone scripts cannot:\n\n- [`getActiveSpreadsheet()`](/apps-script/reference/spreadsheet/spreadsheet-app#getActiveSpreadsheet()), [`getActiveDocument()`](/apps-script/reference/document/document-app#getActiveDocument()), [`getActivePresentation()`](/apps-script/reference/slides/slides-app#getactivepresentation), and [`getActiveForm()`](/apps-script/reference/forms/form-app#getActiveForm()) allow bound scripts to refer to their parent file without referring to the file's ID.\n- [`getUi`](/apps-script/reference/spreadsheet/spreadsheet-app#getUi()) lets bound scripts access the user interface for their parent file to add [custom menus, dialogs, and sidebars](#custom_menus_dialogs_and_sidebars).\n- In Google Sheets, [`getActiveSheet()`](/apps-script/reference/spreadsheet/spreadsheet-app#getActiveSheet()), [`getActiveRange()`](/apps-script/reference/spreadsheet/spreadsheet-app#getActiveRange()), and [`getActiveCell()`](/apps-script/reference/spreadsheet/sheet#getActiveCell()) let the script determine the user's current sheet, selected range of cells, or selected individual cell. [`setActiveSheet(sheet)`](/apps-script/reference/spreadsheet/spreadsheet-app#setActiveSheet(Sheet)) and [`setActiveRange(range)`](/apps-script/reference/spreadsheet/spreadsheet-app#setActiveRange(Range)) let the script change those selections.\n- In Google Docs, [`getActiveTab()`](/apps-script/reference/document/document#getActiveTab()), [`getCursor()`](/apps-script/reference/document/document#getCursor()), and [`getSelection()`](/apps-script/reference/document/document#getSelection()) let the script determine the user's current tab, position of the user's cursor, or selected text. [`setActiveTab(tabId)`](/apps-script/reference/document/document#setActiveTab(String)), [`setCursor(position)`](/apps-script/reference/document/document#setCursor(Position)) and [`setSelection(range)`](/apps-script/reference/document/document#setSelection(Range)) let the script change those selections.\n\nFor more information, see the\n[guide to extending Google Sheets](/apps-script/guides/sheets) or\nthe [guide to extending Google Docs](/apps-script/guides/docs).\n| **Note:** These methods are only available to bound scripts run from the script editor, menu items, dialogs, sidebars, or triggers. When a bound script is run as a web app or via the [Apps Script API](/apps-script/api/how-tos/execute), these methods are not available.\n\nCustom menus, dialogs, and sidebars\n\nBound scripts can customize Google Sheets, Docs, and Forms by adding\n[custom menus](/apps-script/guides/menus) and\n[dialog boxes or sidebars](/apps-script/guides/dialogs). Keep in mind,\nhowever, that a script can only interact with the user interface for the\ncurrent instance of an open file. That is, a script bound to one document\ncannot affect the user interface of another document.\n| Add-ons can also add custom menus, dialogs and sidebars. It is recommended to develop add-ons using [standalone scripts](/apps-script/guides/standalone).\n\nTriggers\n\nBound scripts can use [simple triggers](/apps-script/guides/triggers)\nlike the special `onOpen()` function, which runs automatically whenever a file\nis opened by a user who has edit access. Like all types of scripts, they can\nalso use [installable triggers](/apps-script/guides/triggers/installable).\n\nCustom functions\n\nA [custom function](/apps-script/guides/sheets/functions) is a function in a\nscript bound to Google Sheets that you call directly from a cell using the\nsyntax `=myFunctionName()`. Custom functions are thus similar to the hundreds of\n[built-in functions](https://support.google.com/drive/topic/1361471) in Sheets\nlike [`AVERAGE`](https://support.google.com/drive/answer/3093615) or\n[`SUM`](https://support.google.com/drive/answer/3093669) except that you define\nthe custom function's behavior.\n\nAccess to bound scripts\n\nOnly users who have permission to edit a container can run its bound script.\nCollaborators who have only view access can't open the script\neditor, although if they make a copy of the container file, they become the\nowner of the copy and can see and run a copy of the script.\n\nTo learn how to share a script's container file, refer to [Share files from\nGoogle Drive](https://support.google.com/drive/answer/2494822).\n| All container-bound scripts use the same owner, viewer, and editor access list defined for the container file. The container owner takes ownership of a new script project regardless of who created it."]]
